Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #110457

Pro League·Regular Season - 6
Al-Faisaly FC crest
Al-Faisaly FCHOME
2:1
Match Finished
HT 1-0
Al-Fayha crest
Al-FayhaAWAY
Sat, Oct 14 · 17:00 UTCUnknownRefereeSultan Al-Harbi

◆ 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-Faisaly FC

4-2-3-1
  1. Mustafa MalayekahG
  2. Player 44465M
  3. Player 44450D
  4. Player 44504D
  5. Igor RossiD
  6. Player 44456M
  7. Mohammed AbusabaanM
  8. Player 44464M
  9. Sultan Al GhannamD
  10. Player 44467M
  11. Mohammed MajrashiF

Al-Fayha

4-2-3-1
  1. Player 134996
  2. Mohammed Al BaqawiD
  3. Player 44655
  4. Player 44654D
  5. E. IzaguirreD
  6. Player 104691M
  7. Sami Al Khaibari
  8. R. FernándezF
  9. Player 44659M
  10. Player 44670M
  11. Player 13897M

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 2017-10-13T17: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.

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