Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1197117

First League·Conference League Play-off Group - 4
Slavia Sofia crest
Slavia SofiaHOME
3:1
Match Finished
HT 2-1
Botev Plovdiv crest
Botev PlovdivAWAY
Mon, May 20 · 17:15 UTCUnknown18°CRefereeG. Davidov

◆ 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

Slavia Sofia

4-1-4-1
  1. S. VutsovG
  2. Player 11156D
  3. Player 11103D
  4. Player 334569D
  5. Player 10869D
  6. I. SoletM
  7. T. TasevM
  8. Player 368159M
  9. Player 11058M
  10. Player 10686M
  11. Player 11311F

Botev Plovdiv

4-2-3-1
  1. D. KajzerG
  2. Player 407073D
  3. I. VidevD
  4. A. ChernevD
  5. E. UkakiD
  6. Antonio PereraM
  7. Y. KarabelyovM
  8. Player 266396M
  9. Player 11083M
  10. C. NwachukwuM
  11. M. SekulićF

Botev Plovdiv 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 2024-05-19T17:15: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.

4576fcf6d00e95d2a6df57d9f8c5ae386899ab3dce96f11ebfe0df1c0ce3853a
✓ 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.