SPX Quant Engine · Match Research Note · #1489583


◆ SPX Quant Forecast
Outcome Probabilities
Confidence 4 out of 5 confidenceHome
Jablonec II
57%
Draw
Draw
20%
Away
Ústí nad Orlicí
22%
Model call: Jablonec II
Probability Evolution
How model confidence shifts across the 8-stage match lifecycle
Jablonec II
1
Ústí nad Orlicí
1
Model called (T−24h)
Jablonec II (57%)
Actually happened
Draw (21%)
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
Jablonec II
Player 552209
Player 552106
Player 552125
Player 552076
Player 552105
Player 552217
Player 552165
Player 552124
Player 552057
Player 552056
Player 552103
Ústí nad Orlicí
Player 552179
Player 552087
Player 552163
Player 552180
Player 552033
Player 551940
Player 552158
Player 551948
Player 552094
Player 551949
Player 624723
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.