Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #598482

Liga II·
Ripensia Timisoara crest
Ripensia TimisoaraHOME
4:2
Match Finished
HT 2-0
Turris-Oltul T. Măgurele crest
Turris-Oltul T. MăgureleAWAY
Sat, Oct 31 · 09:00 UTCStadionul ElectricaRefereeI. Demetrescu

◆ 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

Ripensia Timisoara

  1. Player 42641
  2. Player 112848
  3. Player 42650
  4. Player 268135
  5. Player 42870
  6. Andrei Macritchii
  7. Player 42678
  8. Player 42748
  9. Player 143878
  10. Player 273820
  11. Player 61337

Turris-Oltul T. Măgurele

  1. Player 130133
  2. Player 43298
  3. Player 130134
  4. Player 127326
  5. Player 162346
  6. Player 42519
  7. Player 97015
  8. Player 42580
  9. Player 42496
  10. Player 43314
  11. Player 96891

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

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