Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1398261

Segunda Liga·
Lusitânia Lourosa crest
Lusitânia LourosaHOME
1:2
Match Finished
HT 1-0
Torreense crest
TorreenseAWAY
Sat, May 9 · 19:30 UTCEstádio do Lusitânia FC13°CRefereeC. Pereira

◆ 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

Lusitânia Lourosa

3-4-3
  1. Player 306040G
  2. Player 41937D
  3. Josué SáD
  4. Player 426290D
  5. Luis RochaD
  6. Player 550952
  7. Player 279631M
  8. Player 67236M
  9. Rodrigo MartinsF
  10. Player 141295F
  11. Player 96360F

Torreense

4-3-3
  1. Lucas PaesG
  2. Javi VázquezD
  3. Mohamed Ali DiadiéD
  4. StopiraD
  5. Player 41436D
  6. Player 550941
  7. Player 566913
  8. Alejandro AlfaroM
  9. Dany JeanF
  10. M. DrammehF
  11. Player 369481M

Lusitânia Lourosa 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 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.

00214bd48eaf4e36b1a0b855b6107afcbfe883a39f404686b1d682e67d0e5411
✓ 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.