Our method
How We Verify Where Our Numbers Come From
Every figure on this site is read from the game's own information panel, at a named casino, on a recorded date. No estimates, no aggregation, no third-party feeds.
How our figures differ
We publish what the casino is running.
TopSlotsRTP
- Read from the game itself, at a named casino
- Every figure carries the date it was taken
- Studio ceiling and deployed build both shown
- Gaps published, not smoothed over
- We say so when we don't know
Most other sites
- Studio specification repeated as fact
- No date attached to anything
- No casino named against the number
- Version differences invisible
- A ceiling presented as a guarantee
RTP is not a fixed number
Casinos choose from RTP presets
Studios certify their games in several configurations — commonly a headline build plus one or two reduced ones — and each operator licenses whichever suits its commercial position. The reels, the bonus round and the maximum win are identical across all of them. Only the return changes, and nothing on screen indicates which you've opened.
Demo mode can differ from real money
A demo loaded from a casino's lobby usually reflects that operator's configuration, but not always. Some demos serve the studio's default build regardless of what the casino runs for real-money play. Where the two disagree, the real-money client is the one that matters.
There is no central registry
No regulator, studio or third party publishes a list of which operator runs which build. The figure exists in exactly one place: inside the game, at that casino, at that moment. Which is why compiling it means checking each combination individually.
Only the game knows the real RTP
Every studio hides it somewhere different
There's no standard location for the figure. Knowing where each developer puts it is most of the work.
The most common location. Open the paytable from the game's menu and scroll to the end — the return to player is usually printed below the symbol values, often in small type alongside the ways-to-win count and the minimum and maximum stake.
The Verification Process
Every figure on the site goes through the same five steps. It is slow, it is manual, and there is no version of it that runs overnight.
We start from games people actually search for and play rather than attempting to cover every title in existence. Each entry records the name, studio, and the studio's certified return — the ceiling any casino can license up to.
Every operator organises its lobby differently, and game URLs are rarely guessable. Locating a specific title across a set of casinos is manual work, and it's the step that limits how fast coverage grows.
The figure only exists in a running client, so the game has to be opened. Where a casino offers demo play, that's usually sufficient. Where it doesn't, or where the demo appears to serve a studio default rather than the operator's build, a funded account is required to see what a player actually gets.
Faster, no deposit required, and adequate for most operators. Carries one risk: some demos load the studio's default configuration rather than the casino's licensed one.
Slower and requires a funded account, but shows exactly what a paying player sees. This is what we use when a demo isn't offered or looks inconsistent.
Open the paytable, info screen or help file — whichever that studio uses — and read the return to player. This takes seconds once you know where a developer puts it, and considerably longer the first time you encounter one.
The figure is logged against the slot, the casino and the date. It's compared against the studio's certified ceiling, and where the deployed build sits lower, that gap is published as-is. Anything that looks anomalous is rechecked before it goes live rather than after.
Lobby layouts, game availability and panel formats vary between every operator and every studio. There is no universal procedure, which is why this is slow and why sites publishing thousands of casino-specific figures overnight are not doing what they claim to be doing.
If we can't read it from the game, we don't publish it. Where a figure is the studio's specification rather than a verified deployed build, we label it as such.
Why things sometimes go wrong
Manual verification has failure modes, and a methodology page that hides them isn't worth reading.
We would rather publish a smaller number of figures we've actually looked at than a large number we've inferred. When we can't verify something, it stays out of the database until we can. That's the whole trade this site makes.
Work in Progress
Coverage grows one game and one casino at a time, because that's the only way this data can be collected. We prioritise the slots people search for most and the operators most players actually use, then widen outward.
That means the database is smaller than sites publishing studio specifications alone. Deliberately so — those sites are publishing a ceiling and presenting it as a fact, which is precisely the confusion this site exists to clear up.
Rechecks run on a rolling basis, weighted toward popular games and operators known to switch builds. If there's a slot or casino you'd like covered, or a figure that doesn't match what you're seeing in the game, tell us — reader corrections are genuinely useful, and the paytable in front of you is more current than anything we publish.
FAQs
What data do you actually publish?
Do you check in demo mode or with real money?
Is your coverage complete?
How fresh are the figures?
Does RTP vary by country?
What happens if you can't read the RTP?
Can I request a slot or casino?
Written by Mark Gruetze, RTP & Volatility Analyst · Reviewed by Jon Pill · Last updated Jul 2026