Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #852990

Segunda División·
San Antonio Unido crest
San Antonio UnidoHOME
0:0
Match Finished
HT 0-0
Independiente crest
IndependienteAWAY
Sat, Sep 10 · 19:00 UTCEstadio Municipal de Cartagena Fernando Ross Marchessi13°CRefereeN. Pozo

◆ 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

San Antonio Unido

  1. Matías Bórquez
  2. Player 11953
  3. S. Valencia
  4. Player 193323
  5. Player 11803
  6. Player 12233
  7. Player 70145
  8. Player 298185
  9. Player 11900
  10. Player 12294
  11. Player 311325

Independiente

  1. Player 125833
  2. Player 125846
  3. Player 125891
  4. Player 12184
  5. P. Cabrera
  6. Player 70539
  7. Player 106642
  8. Player 125837
  9. Player 11589
  10. Player 80786
  11. Player 195800

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.

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