Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1392186

Segunda División·
Leganes crest
LeganesHOME
1:2
Match Finished
HT 0-1
Racing Santander crest
Racing SantanderAWAY
Sun, May 10 · 14:15 UTCEstadio Municipal de Butarque14°CRefereeMarta Huerta de Aza, 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

Leganes

4-4-2
  1. Juan SorianoG
  2. Naim GarcíaD
  3. MarvelD
  4. MiquelD
  5. Lalo AguilarD
  6. Juan CruzM
  7. Seydouba CisseM
  8. A. DiawaraM
  9. DukM
  10. Diego GarciaF
  11. Dani RodriguezF

Racing Santander

4-2-3-1
  1. S. ErikssonG
  2. Player 482469D
  3. Pablo RamónD
  4. Manu HernandoD
  5. Álvaro MantillaD
  6. Gustavo PuertaM
  7. M. GueyeM
  8. Iñigo VicenteM
  9. Peio CanalesM
  10. Andrés MartínM
  11. G. GuliashviliF

Racing Santander 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-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.

3904ca02abe424e4cf8313fee390d8909685b161d6ec30d6a7d67288d30c3f56
✓ 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.