Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1392031

Segunda División·Regular Season - 25
Racing Santander crest
Racing SantanderHOME
1:0
Match Finished
HT 0-0
Mirandes crest
MirandesAWAY
Mon, Feb 9 · 19:30 UTCUnknown12°CRefereeManuel Jesus Orellana Cid, 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

Racing Santander

4-2-3-1
  1. Jokin EzkietaG
  2. Player 482469D
  3. F. GonzálezD
  4. Manu HernandoD
  5. Álvaro MantillaD
  6. Gustavo PuertaM
  7. Damián RodríguezM
  8. Suleiman CamaraM
  9. Iñigo VicenteM
  10. Andrés MartínM
  11. G. GuliashviliF

Mirandes

5-3-2
  1. Player 185611G
  2. Fernando MedranoD
  3. Jorge CabelloD
  4. Nikola MarašD
  5. Juan GutiérrezD
  6. Player 489678D
  7. T. HelgueraM
  8. Silvi ClúaM
  9. Ali HouaryM
  10. Carlos Fernández LunaF
  11. Javier HernandezF

Mirandes 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-02-08T19: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.

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