Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1202391

DFB Pokal·1st Round
FC Carl Zeiss Jena crest
FC Carl Zeiss JenaHOME
0:1
Match Finished
HT 0-0
Bayer Leverkusen crest
Bayer LeverkusenAWAY
Wed, Aug 28 · 16:00 UTCUnknown30°CRefereeT. Welz

◆ 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

FC Carl Zeiss Jena

4-4-2
  1. Player 261204G
  2. Player 377060D
  3. Player 25526D
  4. Player 355917D
  5. Player 25231D
  6. Player 261707M
  7. Player 26162M
  8. Player 380807M
  9. Player 25173M
  10. Player 91052F
  11. Player 374784F

Bayer Leverkusen

3-4-2-1
  1. M. KovářG
  2. Edmond Faycal TapsobaD
  3. J. TahD
  4. ArthurD
  5. Jeanuël BelocianM
  6. R. AndrichM
  7. Aleix GarcíaM
  8. N. TellaM
  9. A. AdliF
  10. J. HofmannF
  11. P. SchickF

Bayer Leverkusen 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-08-27T16: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.

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