Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1391427

Premier League·Regular Season - 2
Kryvbas KR crest
Kryvbas KRHOME
2:0
Match Finished
HT 1-0
Metalist 1925 Kharkiv crest
Metalist 1925 KharkivAWAY
Sat, Aug 9 · 10:00 UTCUnknown28°CRefereeViktor Kopievskiy, Ukraine

◆ 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

Kryvbas KR

4-2-3-1
  1. Player 181826G
  2. Player 270225D
  3. Player 419608D
  4. B. KonatéD
  5. J. JurčecD
  6. Rafael BandeiraM
  7. M. ZaderakaM
  8. Player 406224M
  9. Y. TverdokhlibM
  10. A. MykytyshynM
  11. Player 311018F

Metalist 1925 Kharkiv

4-1-4-1
  1. Player 130880G
  2. Player 139024D
  3. A. ShabanovD
  4. Player 264087D
  5. Player 312899D
  6. Player 63682M
  7. D. AntyukhM
  8. Player 442643M
  9. V. KalitvintsevM
  10. Player 153478M
  11. C. MbaF

Metalist 1925 Kharkiv named a modestly stronger XI than its 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 2025-08-08T10:00:00.000Z 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.

addf45d5d7b67d4cb08773b002446b56cf31393cf7e82a361281676416406aa2
✓ 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.