Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1206432

Challenger Pro League·Regular Season - 5
Deinze crest
DeinzeHOME
2:0
Match Finished
HT 0-0
Club Brugge II crest
Club Brugge IIAWAY
Sun, Sep 22 · 14:00 UTCUnknown23°CRefereeL. Willems

◆ 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

Deinze

4-2-3-1
  1. Nacho MirásG
  2. Player 37067D
  3. K. SchuermansD
  4. Denis PrychynenkoD
  5. Player 182753D
  6. Jaime SierraM
  7. G. HendrickxM
  8. J. Van LandschootM
  9. Player 8988M
  10. T. DierckxM
  11. Player 131962F

Club Brugge II

4-2-3-1
  1. D. van den HeuvelG
  2. L. AudoorD
  3. Player 375976D
  4. B. YameogoD
  5. D. De RoeveD
  6. Player 291910M
  7. Lynnt AudoorM
  8. Player 294561M
  9. D. PérezM
  10. J. SpileersM
  11. B. ThoresenF

Club Brugge II 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 2024-09-21T14:00: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.

1ed349f4cc1e16ef5a6edb5c3dc34959ff6970f206bf7c2ff14ddc63edc10755
✓ 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.