Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1392151

Segunda División·Regular Season - 36
Cultural Leonesa crest
Cultural LeonesaHOME
1:2
Match Finished
HT 0-0
Cordoba crest
CordobaAWAY
Sat, Apr 18 · 16:30 UTCUnknown22°CRefereeGorka Etayo Herrera, Spain

◆ 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

Cultural Leonesa

4-4-2
  1. Edgar BadíaG
  2. Player 175439D
  3. Matia Barzic GutiérrezD
  4. Player 181598D
  5. Player 128142D
  6. Player 179183M
  7. Thiago OjedaM
  8. Sergi MaestreM
  9. Iván CaleroM
  10. Diego ColladoF
  11. Player 188350F

Cordoba

4-3-3
  1. Íker Álvarez De EulateG
  2. Ignasi VilarrasaD
  3. Rubén AlvesD
  4. Álex MartínD
  5. Carlos AlbarránD
  6. Daniel RequenaM
  7. Alberto del MoralM
  8. Sergi GuardiolaM
  9. Kevin VillodresF
  10. Player 14488F
  11. Cristian CarracedoF

Cordoba named a notably stronger XI than its 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-04-17T16: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.

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