Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1360230

Ligat Ha'al·Championship Round - 8
Maccabi Netanya crest
Maccabi NetanyaHOME
1:6
Match Finished
HT 1-2
Maccabi Tel Aviv crest
Maccabi Tel AvivAWAY
Mon, May 12 · 17:30 UTCUnknown21°CRefereeI. Frid

◆ 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

Maccabi Netanya

5-3-2
  1. Omer NironG
  2. Player 263224D
  3. Player 269285D
  4. M. DjeteiD
  5. Player 159148D
  6. Heriberto TavaresD
  7. Player 110791M
  8. M. PlakuschenkoM
  9. Player 52729M
  10. Player 477832F
  11. M. LeviF

Maccabi Tel Aviv

4-2-3-1
  1. S. SlugaG
  2. Roy RevivoD
  3. S. LemkinD
  4. N. StojićD
  5. T. AsanteD
  6. I. SissokhoM
  7. Gabi KanikovskiM
  8. Dor TurgemanM
  9. D. PeretzM
  10. O. DavidaM
  11. E. ZahaviF

Maccabi Tel Aviv 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-05-11T17:30: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.

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