Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #705640

2. Bundesliga·Relegation Round
VfL Osnabruck crest
VfL OsnabruckHOME
3:1
Match Finished
HT 2-1
FC Ingolstadt 04 crest
FC Ingolstadt 04AWAY
Sun, May 30 · 11:30 UTCUnknown19°CRefereeTobias Stieler, Germany

◆ 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

VfL Osnabruck

4-2-3-1
  1. Player 26318G
  2. Player 25265D
  3. Player 26326D
  4. L. GugganigD
  5. Player 26331D
  6. Player 26337M
  7. Ludovit ReisM
  8. E. AmenyidoM
  9. S. KerkM
  10. Player 26328M
  11. Player 26341F

FC Ingolstadt 04

4-4-2
  1. F. BuntićG
  2. D. FrankeD
  3. Player 25220D
  4. B. PaulsenD
  5. Player 40360D
  6. Player 25202M
  7. M. StenderaM
  8. R. KraußeM
  9. Filip BilbijaM
  10. F. KayaF
  11. S. KutschkeF

FC Ingolstadt 04 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 2021-05-29T11: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.

831a9a61029f84de9f7da02e7d75cd3e2392af63afae4f1c6256567c92d1e175
✓ 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.