Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1280258

3. Lig - Group 2·
Mazıdağı Fosfatspor crest
Mazıdağı FosfatsporHOME
9:0
Match Finished
HT 3-0
Nevşehir Belediyespor crest
Nevşehir BelediyesporAWAY
Sun, Apr 20 · 12:00 UTC21 Kasım Şehir StadyumuRefereeO. Dolğun

◆ 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

Mazıdağı Fosfatspor

  1. Player 332143
  2. Player 214358
  3. Player 62628
  4. Player 144572
  5. Player 152312
  6. Player 62480
  7. Player 151911
  8. Player 139158
  9. Player 142956
  10. K. Köylü
  11. Player 401958

Nevşehir Belediyespor

  1. Player 519565
  2. Player 519564
  3. Player 519562
  4. Player 488070
  5. Player 143184
  6. Player 488056
  7. Player 136777
  8. Player 506071
  9. Player 390781
  10. Player 506072
  11. Player 506075

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.

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