Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1383961

HNL·Regular Season - 9
NK Lokomotiva Zagreb crest
NK Lokomotiva ZagrebHOME
2:1
Match Finished
HT 1-0
Dinamo Zagreb crest
Dinamo ZagrebAWAY
Sun, Oct 5 · 16:45 UTCUnknown8°CRefereeZ. Lovric

◆ 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

NK Lokomotiva Zagreb

3-4-2-1
  1. J. PosavecG
  2. Player 550609D
  3. Player 550635D
  4. D. KolingerD
  5. M. PajačM
  6. Player 550610M
  7. Player 448492M
  8. M. VešovićM
  9. D. VukovićF
  10. Player 342217F
  11. Player 428414F

Dinamo Zagreb

4-3-3
  1. I. NevistićG
  2. Bruno GodaD
  3. S. McKennaD
  4. K. Théophile-CatherineD
  5. Moris ValinčićD
  6. I. BennacerM
  7. Josip MišićM
  8. D. LjubicicM
  9. A. HoxhaF
  10. D. BeljoF
  11. Mateo LisicaF

Dinamo Zagreb 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 2025-10-04T16:45:00.000Z 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.

9271136f99bc22e680cdc39a7da1219363ec5cf55d18b0c8f5072878fe2e9814
✓ 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.