Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1008661

USL Championship·Regular Season - 39
Hartford Athletic crest
Hartford AthleticHOME
2:2
Match Finished
HT 2-2
Rio Grande Valley crest
Rio Grande ValleyAWAY
Wed, Oct 4 · 23:00 UTCUnknown22°CRefereeJ. Encarnación

◆ 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

Hartford Athletic

  1. Player 171348
  2. Player 411184
  3. Player 73854
  4. Player 32254
  5. Player 50864
  6. Player 212269
  7. Player 207039
  8. Player 262842
  9. Player 199500
  10. Player 140681
  11. Player 125506

Rio Grande Valley

  1. Player 51073
  2. Player 53136
  3. Player 216415
  4. Player 216495
  5. Player 102563
  6. Player 51087
  7. Player 312914
  8. Player 103010
  9. Player 324696
  10. Player 102521
  11. Player 363404

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 2023-10-03T23:00:00.000Z 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.

f9b74e9b79df867cb46c9f87073a41b68502836588eb7c878819f09ffda6eba4
✓ 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.