Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1275208

Druha Liga·
Lokomotiv Kyiv crest
Lokomotiv KyivHOME
0:0
Match Finished
HT 0-0
Metalist 1925 II Kharkiv crest
Metalist 1925 II KharkivAWAY
Sun, May 4 · 09:00 UTCStadion NTK im. B. M. BannikovaRefereeO. Kuzyk

◆ SPX Quant Forecast

Free account

Sign in to read the full archive

The full settled-report archive, SHA256 verification, match facts, the Quant Arena and your personal accuracy dashboard are free — just create an account.

Match Analysis

Timeline, stats, lineups, player ratings and AI insights — live during the match.

SPX xG

Lineup Analysis

Lokomotiv Kyiv

  1. Player 134690
  2. Player 242048
  3. Player 87731
  4. Player 200375
  5. Player 323635
  6. Player 481616
  7. Player 517334
  8. Player 429324
  9. Player 324606
  10. Player 416042
  11. Player 478923

Metalist 1925 II Kharkiv

  1. Player 333299
  2. Player 422248
  3. Player 428320
  4. Player 478512
  5. Player 480346
  6. D. Nagnoynyi
  7. Player 442643
  8. Player 458529
  9. Player 480341
  10. Player 426963
  11. Player 480342

Both sides named an XI close to their recent baseline.

Post-Match Deep Analytics

Key absences, beyond-outcome calls and per-player tactical visuals — the shot-based panels finalize from official match data after full-time.

Shot-quality scatter · pass-success grid · key absences · expected shots · beyond-outcome calls — the full tactical deep-dive is a Premium feature →

Integrity Lock

This report's latest stage was generated at 2026-06-09T02:36:46.517Z and its canonical JSON hashed with SHA256. Each prior stage carries its own hash inside the corresponding tab so you can audit every step independently.

e55f2264b51bcb324127670f94fe7b22fb54ed2c99f930069bb821413acd1217
✓ Hash verified — contents unchanged

Model v4.01 · Public beta: every published forecast is timestamped and model-versioned. When the beta period ends (June 2027), per-fixture pre-kickoff forecasts become immutable under our SHA256 audit policy.

Verify yourself via the API.