Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #741137

Primera División RFEF - Group 1·Group 1 - 38
Racing Ferrol crest
Racing FerrolHOME
2:0
Match Finished
HT 1-0
Internacional de Madrid crest
Internacional de MadridAWAY
Sat, May 28 · 16:30 UTCUnknown25°CRefereeAlberto Fuente

◆ 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

Racing Ferrol

  1. Player 166217
  2. Player 128142
  3. Player 107178
  4. D. Castro
  5. Player 338129
  6. Álex López
  7. Player 47140
  8. J. Viacava
  9. Player 47147
  10. Player 179183
  11. Nathan

Internacional de Madrid

  1. Player 179090
  2. Player 75899
  3. Player 104819
  4. Player 181632
  5. Player 184750
  6. Player 107157
  7. Player 182488
  8. Player 182542
  9. Player 123088
  10. Player 286645
  11. Player 184469

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-05-27T16:30: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.

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