Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1148552

USL League One·
Central Valley Fuego crest
Central Valley FuegoHOME
0:1
Match Finished
HT 0-0
Northern Colorado crest
Northern ColoradoAWAY
Thu, Oct 3 · 02:00 UTCFresno State Soccer StadiumRefereeG. Resendiz

◆ 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.

Match Analysis

Timeline, stats, lineups, player ratings and AI insights — live during the match.

SPX xG

Lineup Analysis

Central Valley Fuego

  1. Player 203440
  2. Player 71986
  3. Player 460901
  4. Player 207043
  5. Player 363170
  6. Player 36266
  7. Player 461146
  8. Player 362643
  9. Player 482527
  10. Player 325076
  11. Player 462728

Northern Colorado

  1. Player 71899
  2. Player 102486
  3. Player 71349
  4. Player 363270
  5. Player 198586
  6. Player 72392
  7. Player 415226
  8. Player 47796
  9. Player 73864
  10. Player 102502
  11. Player 460892

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.

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

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.

23d3580e95bacc6983068d65606518b200bec5795daea6b1bb548b395672bcd6
✓ Hash verified — contents unchanged

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.

Verify yourself via the API.