SPX Quant Engine · Match Research Note · #1544804


◆ SPX Quant Forecast
Outcome Probabilities
Confidence 5 out of 5 confidenceHome
Singapore
79%
Draw
Draw
13%
Away
Mongolia
8%
Model call: Singapore
Probability Evolution
How model confidence shifts across the 8-stage match lifecycle
Singapore
4
Mongolia
0
Model called (T−24h)
Singapore (79%)
Actually happened
Singapore (79%)
Verdict graded against the T-24h locked probability. Click the stage tabs above to compare how the probability evolved.
Match Analysis
Timeline, stats, lineups, player ratings and AI insights — live during the match.
SPX xG
ⓘLineup Analysis
Singapore
4-2-3-1Player 98709G
Player 73363D
Player 35169D
Player 35152D
Player 98562D
Player 73244M
Player 73275M
Player 73269M
Player 73239M
Player 73301F
Player 108513M
Mongolia
3-4-2-1Player 664029
Player 348145D
Player 165542D
Player 542887
Player 370087D
Player 165534M
Player 167966M
Player 167906F
Player 167905F
Player 167946M
Player 551627
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.
Lineup Absence Impact
Lineup confirmed shortly before kickoff
SPX Quant Engine
Beyond Match Outcome
Predictions not yet available for this match
SPX Quant Engine
Shot Creation Profile
Not enough recent-match history to build a shot-creation profile for these teams yet.
SPX Quant Engine
Shot Quality
Shot quality data unavailable for this fixture
SPX Quant Engine
Pass Network
Pass network data unavailable for this fixture
SPX Quant Engine
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.
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.