Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #770287

Campeonato de Portugal Prio - Group D·
União Idanhense crest
União IdanhenseHOME
0:5
Match Finished
HT 0-2
Condeixa crest
CondeixaAWAY
Sat, Jan 29 · 15:00 UTCEstádio Municipal de Idanha-a-NovaRefereeDiogo Trancadas

◆ 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

União Idanhense

  1. Player 345510
  2. Player 96562
  3. Player 142756
  4. Player 193221
  5. Player 119613
  6. Player 175405
  7. Player 196565
  8. Player 279486
  9. Player 331874
  10. Player 125549
  11. Player 353000

Condeixa

  1. Player 64266
  2. Player 142048
  3. Player 119602
  4. Player 206291
  5. Player 279287
  6. Player 168536
  7. Bernardo Lourenço
  8. Player 331870
  9. Player 103544
  10. Player 330915
  11. Player 142067

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.

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