Union Berlin vs SV Elversberg Prediction & AI Analysis

Result and Review

Bundesliga, full time: Union Berlin 1–0 SV Elversberg. Here is the pre-kickoff distribution alongside the score it was published against.

• Final score — Union Berlin 1–0 SV Elversberg
• Model's leading outcome before kickoff — Union Berlin win, roughly 42%
• Union Berlin win — the simulation gives roughly 42%
• Draw — the simulation gives roughly 24%
• SV Elversberg win — the simulation gives roughly 34%
• Verdict — hit: the leading outcome matched the result

Leading outcome before kickoff: Union Berlin win, roughly 42%. It landed — 1–0.

Reading the Split

The model leans towards Union Berlin win at 42%, 8 points ahead of SV Elversberg win at 34%. There is a direction here, but not a wide one.

Across the 351 match pages published on this site, the median favourite carries 51%. This one's 42% sits below it — harder to separate than the fixture we typically publish.

The simulated goal averages are Union Berlin 1.72 and SV Elversberg 1.55, 3.27 between them, with the scoring expectation tilted towards Union Berlin. That total is close to the 3.29 median across our published pages.

One thing 42% is not: a statement that this will happen. The remaining 58% belongs to the same distribution and describes matches that get played too. A 42% call that came in every single time would mean the number had been written wrong, not that the model is strong.

Where the Result Landed in the Distribution

The outcome that landed was Union Berlin win — the top line of the pre-match distribution, at 42%. Landing does not make that 42% anything close to a certainty: the other 58% described matches that were just as available from the same three numbers.

On goals: the simulation totalled 3.27 across the two sides, and the match produced 1.

Union Berlin and SV Elversberg on Earlier Pages

Union Berlin or SV Elversberg has appeared on 4 earlier pages of ours. Each is linked below with the probability split we published at the time and, where the fixture has settled, what the match actually produced.

• 2026-09-20 — Schalke 04 vs SV Elversberg · Schalke 04 47% / Draw 22% / SV Elversberg 31% · finished 0–0, graded a miss
• 2026-09-18 — Bayern Munich vs Union Berlin · Bayern Munich 86% / Draw 9% / Union Berlin 5% · finished 7–0, graded a hit
• 2026-09-13 — SV Elversberg vs Bayern Munich · SV Elversberg 9% / Draw 12% / Bayern Munich 79% · finished 1–2, graded a hit
• 2026-09-11 — Union Berlin vs Schalke 04 · Union Berlin 47% / Draw 22% / Schalke 04 31% · finished 1–3, graded a miss

This Page in the Context of the Bundesliga Record

Context for this page: Bundesliga is a competition we have published 45 times, and 43 of those now have a settled result — 25 hit, 18 miss, 0 void. No percentage is computed here; the counts are above and the full index is one click away.

Why the Miss Column Stays Visible

Any channel can look flawless by publishing only the fixtures that worked out. The counter to that is not a better argument, it is a complete list: every call that went out, settled the same way, in one table anyone can recount. A model that never shows a losing row is not a strong model — it is an incomplete record, and an incomplete record cannot be checked.

Both Ends Pinned Down

Simulation observed at 2026-09-30 02:28 UTC; kickoff at 2026-10-10 13:30 UTC. The prediction was published before kickoff and the timestamp is verifiable, so both ends of this comparison are fixed and neither moved after the whistle.

See It Live

@Oddsflowteam_bot publishes the live signals as they fire, timestamped, on Telegram. The weekly ledger on this site collects the settled rows so the record can be counted rather than described.

Verify This Page Yourself

Both ends of this page are now fixed: the file was written 1 day 15 hours before kickoff (generated 2026-10-08 22:10 UTC, kickoff 2026-10-10 13:30 UTC), and the result was appended only afterwards. An unedited copy of the pre-match numbers sits in the public mirror as record/data/union-berlin-vs-sv-elversberg-1575182.json — browse the public record. The commit history is the more interesting half of that repository: it shows when each number was written down, which is the one part of a record that cannot be reconstructed later. The grading rules behind the verdict above are set out in How We Count Our Record.