Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1436034

Pro League·Regular Season - 14
Al-Hilal Saudi FC crest
Al-Hilal Saudi FCHOME
3:0
Match Finished
HT 1-0
Al-Hazm crest
Al-HazmAWAY
Thu, Jan 8 · 14:55 UTCUnknownRefereeGlenn Nyberg, Sweden

◆ 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-3-3
  1. M. Al RubaieG
  2. Nasser Al DawsariD
  3. Y. AkçiçekD
  4. Hassan TambaktiD
  5. Hamad Al YamiD
  6. Mohammed KannoM
  7. Rúben NevesM
  8. S. Milinković-SavićM
  9. Salem Al DawsariF
  10. Marcos LeonardoF
  11. MalcomF

Al-Hazm

5-4-1
  1. Bruno VarelaG
  2. Ahmed Al NakhliD
  3. Abdelmounaim BoutouilD
  4. Sultan TankerD
  5. Abdulrahman Al DakheelD
  6. Mohammed Essa Harbush
  7. Fábio MartinsM
  8. Basil Al SayyaliM
  9. L. RosierM
  10. A. BahM
  11. Nawaf Al HabashiF

Al-Hilal Saudi FC 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 2026-01-07T14:55: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.

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