Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #657872

Pro League·Regular Season - 29
Al-Fateh crest
Al-FatehHOME
3:0
Match Finished
HT 1-0
Al-Qadisiyah FC crest
Al-Qadisiyah FCAWAY
Tue, May 25 · 18:00 UTCUnknown28°CRefereeSultan Al-Harbi

◆ 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

Al-Fateh

4-2-3-1
  1. Maksym KovalG
  2. Tawfiq BuhumaidD
  3. M. SaâdaneD
  4. Ammar Al DuhaimD
  5. Nawaf BoushalD
  6. Mohammed Al FuhaidM
  7. S. BendebkaM
  8. H. SoudaniM
  9. C. CuevaM
  10. M. BatnaM
  11. Player 38712F

Al-Qadisiyah FC

4-2-3-1
  1. Player 44328G
  2. Ibrahim Al ShuaylD
  3. Khalifah Al DawsariD
  4. U. VitasD
  5. Hamad Al YamiD
  6. Abdulrahman Al SafriM
  7. Naif HazaziM
  8. Hassan Al AmriM
  9. Player 44670M
  10. S. OhawuchiM
  11. Player 3156F

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 2021-05-24T18: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.

9857ac7e07c4ab46f3a47caa2f61140d1f8e70df2df5109b5b7eba6d4a1a26a1
✓ 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.