Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1207998

King's Cup·
Al Taee crest
Al TaeeHOME
5:2
Match Finished
HT 1-0
Al Khaleej Saihat crest
Al Khaleej SaihatAWAY
Mon, Sep 23 · 15:45 UTCPrince Abdul Aziz bin Musa'ed Stadium31°CRefereeTurki Al-Hashlan

◆ 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 Taee

4-1-4-1
  1. Moataz Al BaqaawiG
  2. Hussain QasimD
  3. Ibrahim Al NakhliD
  4. Bander WhaeshiD
  5. Abdulaziz Al FarajD
  6. Ahmed Al JuwaidM
  7. Abdulrahman Al HarthiM
  8. Player 3342M
  9. E. BandaM
  10. A. CordeaM
  11. L. TawambaF

Al Khaleej Saihat

4-2-3-1
  1. I. ŠehićG
  2. Bandar NasserD
  3. Abdullah Al FahadD
  4. M. TisserandD
  5. Arif Al HaydarD
  6. Murad Al HawsawiM
  7. Khaled Al SamiriM
  8. Fábio MartinsM
  9. Saleh Abu Al ShamatM
  10. Mansor HamziM
  11. Abdullah Al SalemF

Al Taee named a notably 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 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.

355e4ca6f6c0b08fead9e11663f0daeafd8134c24a8445d0267f4c853ac548de
✓ 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.