Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #741103

Primera División RFEF - Group 1·Group 1 - 34
Calahorra crest
CalahorraHOME
1:2
Match Finished
HT 1-1
Internacional de Madrid crest
Internacional de MadridAWAY
Sun, May 1 · 15:00 UTCUnknownRefereeDavid López

◆ 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

Calahorra

  1. Player 116911
  2. Player 107141
  3. Player 123097
  4. Player 125592
  5. Player 181426
  6. Player 122783
  7. Player 70498
  8. Player 181157
  9. Player 122875
  10. Player 122765
  11. Carlos Vicente

Internacional de Madrid

  1. L. Badiashile
  2. Player 182526
  3. Player 104819
  4. Player 122942
  5. Player 107157
  6. Player 137134
  7. Player 182488
  8. Player 162031
  9. Player 122656
  10. Player 123088
  11. Player 181584

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 2022-04-30T15: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.

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