Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1394428

3. Liga·
FC Schweinfurt 05 crest
FC Schweinfurt 05HOME
2:4
Match Finished
HT 1-2
Erzgebirge Aue crest
Erzgebirge AueAWAY
Sat, May 16 · 11:30 UTCWilly-Sachs-Stadion11°CRefereeJ. Besong

◆ 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 Schweinfurt 05

3-4-3
  1. Player 158290G
  2. Player 202741D
  3. Player 585166D
  4. Player 428968D
  5. E. ÇelebiD
  6. Player 177369M
  7. Player 203333M
  8. J. GeisM
  9. Player 26129M
  10. S. MüllerM
  11. Player 327848F

Erzgebirge Aue

4-2-3-1
  1. Player 279979G
  2. J. CollinsD
  3. Player 327987D
  4. R. MaloneD
  5. Player 26426D
  6. Player 334363M
  7. E. MajetschakD
  8. J. Günther-SchmidtF
  9. J. GuttauM
  10. Player 374784M
  11. M. BärF

FC Schweinfurt 05 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-06-09T02:36:46.517Z 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.

8b080e9793e8853300109231e1e576a96c0255dc59846a1d66b093bc09341c31
✓ 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.