Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1206620

Challenger Pro League·Regular Season - 29
SK Beveren crest
SK BeverenHOME
2:2
Match Finished
HT 1-0
Club Brugge II crest
Club Brugge IIAWAY
Sun, Apr 13 · 11:30 UTCUnknown17°CRefereeA. De Beuckelaer

◆ 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

SK Beveren

4-1-4-1
  1. B. ReusG
  2. L. JansD
  3. D. WuytensD
  4. Player 496337D
  5. Player 69374D
  6. J. Van HeckeM
  7. Player 8993M
  8. Player 8988M
  9. C. BrülsM
  10. M. ServaisM
  11. Player 131962F

Club Brugge II

4-2-3-1
  1. Argus Vanden DriesscheG
  2. S. WylinD
  3. Player 371524D
  4. V. OsujiD
  5. Lynnt Audoor
  6. Player 387517M
  7. Player 291910M
  8. Player 294561M
  9. Player 375976M
  10. Player 426446M
  11. Player 482302F

SK Beveren 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-04-12T11: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.

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