Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1493555

USL Championship·Group Stage
Charleston Battery crest
Charleston BatteryHOME
4:1
Match Finished
HT 2-0
Loudoun United crest
Loudoun UnitedAWAY
Wed, Jun 24 · 23:00 UTCPatriots Point Soccer Complex, 27°CRefereeK. Broadley

◆ SPX Quant Forecast

Free account

Sign in to read the full archive

The full settled-report archive, SHA256 verification, match facts, the Quant Arena and your personal accuracy dashboard are free — just create an account.

AI Match Report · Engine Read

48 hours out the Engine favored Charleston Battery (47%), and the live read grew to 100% by the 75-minute checkpoint as the match bore it out. Final: 4-1, a Charleston Battery win.

What we grade: only the forecast we SHA256-stamped before kickoff — the number on the public record. That was Charleston Battery (a lean, not a strong call), so this match is a hit in our published record. The in-play line is shown for transparency, never graded after the fact.

SPX xG

Lineup Analysis

Starting XI not yet confirmed — lineups land roughly an hour before kickoff and this report updates automatically.

Post-Match Deep Analytics

Two lifecycle groups: pre-match signals (available before kickoff) and per-player analytics that finalize from official match data after full-time.

Shot-quality scatter · pass-success grid · key absences · expected shots · beyond-outcome calls — the full tactical deep-dive is an Engine Room feature →

Integrity Lock

This report's latest stage was generated at 2026-06-20T17:15:05.612Z and its canonical JSON hashed with SHA256 — locked at lineup confirmation. Each prior stage carries its own hash inside the corresponding tab so you can audit every step independently.

1518dcf1b1987d923b061e9987e77a5aaec38168732ec37f76e13a6181472744
✓ Hash verified — contents unchanged

Model v4.56 · 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.

Verify yourself via the API.