Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1392729

Challenger Pro League·Regular Season - 23
K. Lierse S.K. crest
K. Lierse S.K.HOME
1:2
Match Finished
HT 1-1
Beerschot VA crest
Beerschot VAAWAY
Sun, Feb 1 · 12:30 UTCUnknown9°CRefereeK. Clerkx

◆ 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

K. Lierse S.K.

5-3-2
  1. Player 297976G
  2. Player 551268
  3. Player 481509D
  4. Player 174829D
  5. Player 551315
  6. Player 551282D
  7. E. MatutaM
  8. D. AsareM
  9. N. Mayoka-TikaM
  10. Player 551316
  11. A. StanićF

Beerschot VA

3-4-1-2
  1. Nick ShintonG
  2. B. PlatD
  3. B. Van den EyndenD
  4. C. DagbaD
  5. Glenn ClaesM
  6. L. Van EenooM
  7. G. HaraguchiM
  8. Dennis GyamfiM
  9. D. Wright-PhillipsF
  10. A. Vula
  11. Ensar BrahićF

K. Lierse S.K. 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-01-31T12: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.

46becd29b24cbd563bbd242221c3e718e0fccfca970858d66aed31eea4eb92cc
✓ 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.