Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1252664

Pro League·Regular Season - 28
Al-Hilal Saudi FC crest
Al-Hilal Saudi FCHOME
3:0
Match Finished
HT 1-0
Al Khaleej Saihat crest
Al Khaleej SaihatAWAY
Thu, Apr 17 · 15:50 UTCUnknown28°CRefereeS. Gözübüyük

◆ 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-Hilal Saudi FC

4-2-3-1
  1. Mohammed Al OwaisG
  2. Moteb Al HarbiD
  3. Hassan TambaktiD
  4. K. KoulibalyD
  5. Yasser Al ShahraniD
  6. S. Milinković-SavićM
  7. Rúben NevesM
  8. Salem Al DawsariM
  9. MalcomM
  10. Kaio CésarM
  11. A. MitrovićF

Al Khaleej Saihat

4-2-3-1
  1. Raed OzaybiG
  2. Pedro RebochoD
  3. Mohammed Al KhabraniD
  4. D. KourbelisD
  5. Saeed Al HamsalD
  6. Murad Al HawsawiM
  7. Mansor HamziM
  8. Fábio MartinsM
  9. K. FortounisM
  10. T. MurgM
  11. Abdullah Al SalemF

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 2025-04-16T15:50: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.

655ad91a29e867d256732e3506202bd60ec2cd1365bdb34d13594600b1830548
✓ 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.