Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1391942

Segunda División·Regular Season - 17
Real Sociedad II crest
Real Sociedad IIHOME
0:1
Match Finished
HT 0-0
Sporting Gijon crest
Sporting GijonAWAY
Sat, Dec 6 · 17:30 UTCUnknown14°CRefereeEder Mallo Fernandez, 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

Real Sociedad II

4-1-4-1
  1. Aitor FragaG
  2. Jon BaldaD
  3. Player 551408D
  4. Player 197209D
  5. Player 438271D
  6. Tomy CarbonellM
  7. Job OchiengM
  8. Ibai AguirreM
  9. Player 551356M
  10. Lander AstiazaranM
  11. Gorka Carrera ZarranzF

Sporting Gijon

4-2-3-1
  1. Rubén YáñezG
  2. Diego SánchezD
  3. L. PerrinD
  4. Eric CurbeloD
  5. Guille RosasD
  6. Nacho MartínM
  7. Justin SmithM
  8. Dani QueipoM
  9. Álex CorrederaM
  10. César GelabertM
  11. F. OteroF

Sporting Gijon 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 2025-12-05T17: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.

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