Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1288337

AFC Champions League Elite·League Stage - 3
Al-Rayyan SC crest
Al-Rayyan SCHOME
1:2
Match Finished
HT 0-2
Al-Ahli Jeddah crest
Al-Ahli JeddahAWAY
Mon, Oct 21 · 18:00 UTCUnknown29°CRefereeAhmad Al Ali

◆ 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-Rayyan SC

3-4-3
  1. Paulo VictorG
  2. David GarcíaD
  3. André AmaroD
  4. Player 16883D
  5. Hazem ShehataM
  6. J. De SartM
  7. Player 2533M
  8. J. BrenetM
  9. TrézéguetF
  10. Roger GuedesF
  11. Player 20666F

Al-Ahli Jeddah

4-2-3-1
  1. Abdulrahman Al SanbiG
  2. Saad YaslamD
  3. IbañezD
  4. M. DemiralD
  5. Ali MajrashiD
  6. F. KessiéM
  7. Ali Al AsmariM
  8. Firas Al BrikanM
  9. Gabri VeigaM
  10. R. MahrezM
  11. I. ToneyF

Al-Ahli Jeddah 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 2024-10-20T18: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.

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