SPX Quant Engine · Match Research Note · #1487449


◆ SPX Quant Forecast
Outcome Probabilities
Confidence 5 out of 5 confidenceHome
Sigma Olomouc II
66%
Draw
Draw
15%
Away
Blansko
19%
Model call: Sigma Olomouc II
Probability Evolution
How model confidence shifts across the 8-stage match lifecycle
Sigma Olomouc II
5
Blansko
0
Model called (T−24h)
Sigma Olomouc II (65%)
Actually happened
Sigma Olomouc II (65%)
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
Sigma Olomouc II
Adrian Malovec
Player 465069
S. Jalovicor
Player 646402
D. Drabek
Player 66373
Player 66292
Player 574413
P. Siegl
Player 420359
Player 210180
Blansko
Player 574429
Player 574419
Player 574452
Player 66418
Player 574422
Player 574463
Player 574232
Player 574497
Player 555389
Player 574421
Player 574236
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.