Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #770391

Campeonato de Portugal Prio - Group E·
Sacavenense crest
SacavenenseHOME
2:1
Match Finished
HT 1-0
Coruchense crest
CoruchenseAWAY
Sun, Feb 13 · 15:00 UTCComplexo Desportivo Elias Pereira Campo 114°CRefereeJoel Martins

◆ 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

Sacavenense

  1. Player 142393
  2. Player 142453
  3. Player 141425
  4. Player 279400
  5. Player 310921
  6. Player 92074
  7. Player 123901
  8. Player 279311
  9. Player 142383
  10. Player 142748
  11. Player 279403

Coruchense

  1. Player 334000
  2. Player 332369
  3. Player 142347
  4. Player 279439
  5. Player 332373
  6. Player 332378
  7. Player 119610
  8. Player 152682
  9. Player 179675
  10. Player 332377
  11. Player 332381

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.

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