SPX Quant Engine · Match Research Note · #1518099


◆ SPX Quant Forecast
Outcome Probabilities
Confidence 4 out of 5 confidenceHome
Hồng Lĩnh Hà Tĩnh
60%
Draw
Draw
25%
Away
Da Nang
16%
Model call: Hồng Lĩnh Hà Tĩnh
Probability Evolution
How model confidence shifts across the 8-stage match lifecycle
Hồng Lĩnh Hà Tĩnh
0
Da Nang
0
Model called (T−24h)
Hồng Lĩnh Hà Tĩnh (60%)
Actually happened
Draw (25%)
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
Hồng Lĩnh Hà Tĩnh
Player 531654
Player 65202
Player 531568
Player 531681
Player 531678
Player 531614
Player 531513
Player 357112
Player 531511
Player 293109
Player 301884
Da Nang
Player 65018
Player 531564
Player 531546
Player 65199
Player 531587
Player 644174
Player 16563
Player 201563
M. Makarić
Player 414071
Player 531537
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.