A changelog of confirmed RTP changes: which casino raised or lowered the payout setting of which slot, confirmed across two consecutive catalogue snapshots, with a per-casino downgrade leaderboard and RSS feed.
Providers ship the same slot in several RTP configurations (96%, 94%, 92% and lower) and each casino picks which build to run — and can switch it silently. RTP Watch re-reads the per-casino RTP configuration of every game in our catalogue on every collector round and diffs it against the previously published value. A change is published only after it survives two consecutive snapshots; a value that reverts in between is discarded as a source flap. Currently 2,673 game–casino pairs across 1,448 games are tracked, last checked 2026-10-01.
Last 30 days: 0 confirmed downgrades and 1 confirmed upgrades across all tracked casinos.
| Date | Casino | Game | Provider | Old RTP | New RTP | Change |
|---|---|---|---|---|---|---|
| 2026-09-10 | Stake | Golden Ox | Endorphina | 96% | 96.63% | upgrade (+0.63pp) |
We only see the casinos and games in our catalogue snapshot — currently six operators and the roughly 400 titles where we have per-casino RTP measurements. A change at a casino we do not cover, or in a game with a single measured build, is invisible to this page. RTP is also a long-run statistical property, not a promise for any session: a downgrade from 96.5% to 94.0% roughly multiplies the house edge (3.5% → 6.0%), but short-term results still dominate variance.
Static per-casino comparison in the RTP builds report; the 50 most recent events as RSS at /api/rtp-watch/feed.xml.
A single scrape can be wrong — a provider page can serve a placeholder, a default build or a cached variant. Publishing a downgrade that never happened would mislabel a casino, so every change must survive two consecutive collector rounds before it is shown. The cost is a delay of one round; the benefit is that everything on this page actually happened.
No. Running a lower RTP build is legal and disclosed in the provider's game rules — the problem is that casinos switch builds silently and the displayed value is buried in a help file most players never open. A downgrade is a pricing change, not rigged software; this page exists so the pricing change is at least visible.
The collector runs on the same schedule as our other data rounds. The "last run" timestamp above the changelog shows when the most recent check completed; the confirmation rule means an event appears at the earliest on the second round after the actual switch.
Yes — the 50 most recent confirmed events are published as an RSS 2.0 feed at /api/rtp-watch/feed.xml, one item per event with the game, casino, old and new RTP and the detection date.