SPX Quant Engine · Match Research Note · #1513132


◆ SPX Quant Forecast
Outcome Probabilities
Confidence 4 out of 5 confidenceHome
Huntsville City
57%
Draw
Draw
20%
Away
Connecticut FC
23%
Model call: Huntsville City
Probability Evolution
How model confidence shifts across the 8-stage match lifecycle
Huntsville City
2
Connecticut FC
2
Model called (T−24h)
Huntsville City (58%)
Actually happened
Draw (20%)
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
Huntsville City
Player 369898
J. Gaines
Player 645892
Player 413209
Player 541931
Player 655123
Player 334601
N. Pariano
A. Jarvis
Player 645540
Player 542332
Connecticut FC
Player 543411
R. van Hees
Player 644840
Player 644873
Player 316791
A. Monis
Player 644841
Player 646431
Player 644839
Player 618391
Player 359453
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.