Published forecasts

Every forecast we have published, in the order we published it. Each row carries a hash of itself and the row before, so changing a probability after a match has been played would break every hash after it. That is what stops us quietly revising a number and claiming we always said it — and you do not have to take our word for the check, it runs when you load this page.

The published forecasts for Anderlecht v Zulte Waregem

These are the forecasts we published for this fixture, hash-chained so a number we wrote before kick-off cannot be quietly changed afterwards.

← Back to the full record

Chain intact across all 2034 published forecasts.

Daily seals

At the end of each day we write that day's final hash to separate storage. The chain alone would catch a single altered forecast, but not a wholesale rebuild from edited rows — evidence kept in the same place as the thing it attests to proves less than it appears to. Note a seal today and you can hold us to it later.

#PublishedMatchH / D / AResultHash
18662026-09-13 04:06Anderlecht vZulte Waregem55% / 22% / 23%our call landedwe called home 55% · home winf69a2b46523a…
15172026-09-12 13:07Anderlecht vZulte Waregem56% / 22% / 22%our call landedwe called home 56% · home win227d6e1dd35a…
13302026-09-09 21:05Anderlecht vZulte Waregem56% / 22% / 22%our call landedwe called home 56% · home win1abdd413dcbc…

The result column pairs the outcome we called (our most-likely of home / draw / away, with its probability) against what actually happened — a verdict, not a score: a 60% call missing is not a failure. Whether the probabilities are any good is a separate question, answered on the accuracy page. This page only shows that we have not changed our mind about them afterwards.