Brest vs Nice Prediction & AI Analysis

Prediction Against Result

Brest 1–2 Nice, Ligue 1. Below is what this page published before kickoff, set next to what actually happened.

• Final score — Brest 1–2 Nice
• Model's leading outcome before kickoff — Brest win, roughly 43%
• Brest win — the simulation gives roughly 43%
• Draw — the simulation gives roughly 24%
• Nice win — the simulation gives roughly 33%
• Verdict — miss: the leading outcome did not come in

The model's leading outcome was Brest win at roughly 43%. It did not come in — the match finished 1–2. That is a miss, and it stays on the record as one.

Reading the Split

The model leans towards Brest win at 43%, 10 points ahead of Nice win at 33%. 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 43% sits below it — harder to separate than the fixture we typically publish.

The simulated goal averages are Brest 1.74 and Nice 1.52, 3.26 between them, with the scoring expectation tilted towards Brest. That total is close to the 3.29 median across our published pages.

One thing 43% is not: a statement that this will happen. The remaining 57% belongs to the same distribution and describes matches that get played too. A 43% 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 Nice win, which the model had at 33%, behind Brest win on 43%. That is a miss and it is counted as one. An outcome given 33% is supposed to occur at roughly that frequency; it occurred here. What that changes is which column this row sits in — not how the pre-match numbers should have been written.

On goals: the simulation totalled 3.26 across the two sides, and the match produced 3.

Brest and Nice on Earlier Pages

Brest or Nice 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-10-18 — Lyon vs Nice · Lyon 58% / Draw 22% / Nice 20% · finished 2–1, graded a hit
• 2026-10-17 — Lille vs Brest · Lille 59% / Draw 22% / Brest 19% · finished 1–1, graded a miss
• 2026-10-11 — Nice vs Strasbourg · Nice 43% / Draw 25% / Strasbourg 32% · finished 2–1, graded a hit
• 2026-10-10 — Brest vs Angers · Brest 50% / Draw 25% / Angers 25% · finished 5–1, graded a hit

Where This Fixture Sits in Our Ligue 1 Record

We have published 45 Ligue 1 match pages, this one included. 38 of them have settled: 24 graded a hit, 14 graded a miss, 0 void. Counts, not a rate — if you would rather count them yourself, they are all at Predictions.

What One Match Proves

A single fixture settles nothing about a model, in either direction. A side with less than an even chance that wins was never a foregone conclusion, and one that loses was never a blunder — the number was a statement about frequency, and frequency only becomes visible over a run of matches. The honest test is the accumulated ledger, which is why every published signal is settled in public instead of the good ones being quoted twice.

Timestamps

The simulation was observed at 2026-10-13 00:37 UTC; kickoff was 2026-10-23 18:45 UTC. The prediction was published before kickoff and the timestamp is verifiable — which is the only reason this comparison is worth printing.

Check the Rest of the Record

Live signals from the same system are published on Telegram through @Oddsflowteam_bot, each timestamped before its match. The weekly ledger on this site lists them line by line — timestamp, market, price, final score, result — with the losses in the same type as the wins.

Verify This Page Yourself

Both ends of this page are now fixed: the file was written 1 day 20 hours before kickoff (generated 2026-10-21 22:10 UTC, kickoff 2026-10-23 18:45 UTC), and the result was appended only afterwards. An unedited copy of the pre-match numbers sits in the public mirror as record/data/brest-vs-nice-1552794.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.