Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1431856

Primera División RFEF - Group 1·Group 1 - 35
Real Madrid II crest
Real Madrid IIHOME
1:0
Match Finished
HT 0-0
Unionistas de Salamanca crest
Unionistas de SalamancaAWAY
Sat, May 2 · 19:00 UTCUnknown

◆ 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

Real Madrid II

  1. Sergio Mestre
  2. Jesús Fortea
  3. Joan Martínez
  4. V. Valdepenas
  5. Diego Aguado Facio
  6. Daniel Yañez
  7. Player 443585
  8. Jorge Cestero
  9. Player 568239
  10. Pol Fortuny
  11. Rachad Dhimi

Unionistas de Salamanca

  1. Player 561056
  2. Player 181417
  3. Player 561054
  4. Player 561055
  5. Player 554334
  6. Player 104927
  7. José Masllorens
  8. Player 349993
  9. Player 575327
  10. Player 554326
  11. Player 185210

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-05-01T19:00: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.

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