Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #254084

AFC Champions League·
Al-Hilal Saudi FC crest
Al-Hilal Saudi FCHOME
4:1
Match Finished
HT 0-1
Pakhtakor crest
PakhtakorAWAY
Wed, Mar 2 · 17:30 UTCPrince Faisal bin Fahd Stadium21°CRefereeNawaf Shukralla, Bahrain

◆ 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

  1. Player 44743
  2. Player 34720
  3. Abdullah Al DossaryD
  4. Mohammed Al BuraykD
  5. Ahmed SharahiliD
  6. Player 104180M
  7. Player 44344M
  8. Carlos EduardoM
  9. Player 44573M
  10. Faisal DarwishD
  11. Ailton

Pakhtakor

  1. Player 73670G
  2. Player 73610D
  3. A. Orahovac
  4. Player 53828
  5. Player 73601D
  6. Player 73453
  7. Player 73535
  8. Player 65576
  9. Player 73781
  10. Player 73496
  11. I. SergeevF

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.

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