Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #947574

Campeonato de Portugal Prio - Group C·
Arronches e Benfica crest
Arronches e BenficaHOME
1:2
Match Finished
HT 1-1
Loures crest
LouresAWAY
Sun, Mar 19 · 15:00 UTCEstadio Municipal Arronches20°CRefereeDaniel 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

Arronches e Benfica

  1. Player 331976
  2. Player 193221
  3. Player 385878
  4. Player 152685
  5. Player 196994
  6. Player 385874
  7. Player 389984
  8. Player 389981
  9. Player 279200
  10. Player 367532
  11. Player 385853

Loures

  1. Player 142696
  2. Player 119521
  3. Player 142413
  4. Player 296143
  5. Player 331954
  6. Player 407291
  7. Player 279409
  8. Player 383221
  9. Player 279170
  10. Player 303551
  11. Player 390778

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.

9c57178e5d9840a776d5e26d6e3c9e7f8d6990601348c625ffd0117e492ca315
✓ 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.