Racing Santander vs Alaves Prediction & AI Analysis

How It Finished

Final score: Racing Santander 2–1 Alaves in the La Liga. The pre-match distribution on this page has not been edited; it is reproduced below against the result.

• Final score — Racing Santander 2–1 Alaves
• Model's leading outcome before kickoff — Racing Santander win, roughly 39%
• Racing Santander win — the simulation gives roughly 39%
• Draw — the simulation gives roughly 27%
• Alaves win — the simulation gives roughly 34%
• Verdict — hit: the leading outcome matched the result

Pre-match, the simulation leaned Racing Santander win at about 39%. Final score 2–1: that lean was right.

Reading the Split

The three numbers sit close together: Racing Santander win tops the list at 39%, with Alaves win only 5 points behind on 34%. The model has barely separated this fixture.

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

The simulated goal averages are Racing Santander 1.42 and Alaves 1.33, 2.75 between them, split almost evenly between the two sides. That total is below the 3.22 median across our published pages.

One thing 39% is not: a statement that this will happen. The remaining 61% belongs to the same distribution and describes matches that get played too. A 39% 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 Racing Santander win — the top line of the pre-match distribution, at 39%. Landing does not make that 39% anything close to a certainty: the other 61% described matches that were just as available from the same three numbers.

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

Our Published La Liga Pages

Our La Liga coverage stands at 29 published pages, of which 29 now carry a result: 16 hit, 12 miss, 1 void. The miss column is printed at the same size as the hit column, and nothing has been filtered out of it. Every page is listed at Predictions.

Reading a Result Honestly

Probabilities are graded in bulk, never one at a time. The useful question after a match is not "was it right" but "does the whole run of calls land where the probabilities said it would" — a run that lands about as often as those numbers implied is a calibrated model, and a run that never misses at all mostly means the numbers were written too timidly. Either way, a single row is a data point, not a verdict.

The Pre-Match Timestamp

Observation timestamp 2026-09-03 06:57 UTC, kickoff 2026-09-12 12:00 UTC. The prediction was published before kickoff and the timestamp is verifiable; the comparison above compares two fixed things, not one fixed thing and one memory.

The Full Ledger

Every live signal from this system goes out on Telegram via @Oddsflowteam_bot with a timestamp attached, and every one is settled afterwards. The weekly ledger on this site is the complete table — wins, losses, halves and voids, all in one place.

Verify This Page Yourself

Both ends of this page are now fixed: the file was written 1 day 13 hours before kickoff (generated 2026-09-10 22:10 UTC, kickoff 2026-09-12 12:00 UTC), and the result was appended only afterwards. An unedited copy of the pre-match numbers sits in the public mirror as record/data/racing-santander-vs-alaves-1570378.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.