Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1451602

First League·Regular Season - 28
Botev Plovdiv crest
Botev PlovdivHOME
5:0
Match Finished
HT 3-0
Spartak Varna crest
Spartak VarnaAWAY
Sat, Apr 4 · 14:00 UTCUnknownRefereeValentin Zhelezov, Bulgaria

◆ 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

Botev Plovdiv

4-2-3-1
  1. D. NaumovG
  2. K. BalogiannisD
  3. Nikola SoldoD
  4. Player 550576
  5. E. KwatengD
  6. Player 639494
  7. Player 180863M
  8. S. KaluM
  9. T. NedelevM
  10. E. RodríguezM
  11. Player 518577F

Spartak Varna

4-2-3-1
  1. Player 131466G
  2. Player 11149D
  3. D. KrastevD
  4. Player 550598
  5. Player 640700D
  6. Player 208473M
  7. Player 199231M
  8. Player 550568
  9. Player 269309M
  10. Player 265673M
  11. T. ChunchukovF

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-04-03T14: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.

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