Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1288120

Tercera División RFEF - Group 10·
Ciudad de Lucena crest
Ciudad de LucenaHOME
6:4
Match Finished
HT 1-1
Inter Sevilla crest
Inter SevillaAWAY
Sun, May 4 · 10:00 UTCEstadio Ciudad de Lucena15°CRefereeRuben Cartes

◆ 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

Ciudad de Lucena

  1. Player 182811
  2. Player 99587
  3. Player 185515
  4. Player 331602
  5. Player 185365
  6. Player 185207
  7. Player 288839
  8. Player 436200
  9. Player 77606
  10. Player 123089
  11. Player 285305

Inter Sevilla

  1. Player 122759
  2. Player 163400
  3. Player 278868
  4. Player 185551
  5. Player 285259
  6. Player 489626
  7. Player 510199
  8. Player 107223
  9. Player 190691
  10. Player 186842
  11. Player 384199

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.

8d1a493d4f614b863b755a5afbe159f893f40cf4df5ce4531a666b1a31b7cb68
✓ 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.