Learn
Same game, different RTP — the idea of a configuration
The RTP on a spec sheet and the RTP in an actual lobby can differ. That is not an error — it is the concept of a configuration, and knowing the structure keeps the two numbers apart.
A game does not have one RTP
When first learning about RTP it is natural to assume one game carries one value. In practice several studios build the same game in multiple RTP configurations and offer them to operators — identical screen and rules, different payback setting: different builds of one game.
The value on a studio spec sheet is therefore usually the default configuration. Nothing guarantees that the build running in a given lobby is the default, so the spec-sheet number is best read as "this game exists at this value" — not "this game pays this everywhere".
The RTP figures in this site's game guides follow the same principle: they are the studio's published default configuration, never a promise about a specific deployment.
What it looks like in a real catalogue
The Play'n GO catalogue this site carries is a good specimen. The studio publishes each game's default RTP alongside the configuration band it belongs to: 456 of 469 titles have their default in the 96 band, with 9 in the 94 band, 3 in the 91 band and one in the 97 band — so even the defaults vary by game.
Each of those games also ships in separate lower-band builds. The 96.18% on the recently reviewed Spice Spice Baby!, for instance, is the default configuration, and lower-configuration builds of the same game exist — which is exactly why that caution line appears in reviews here.
One more number for scale: published default RTPs in this catalogue run from 88.46% to 99.69%. The top end is not slots but table and poker formats where strategy participates — the point where this article meets the earlier one about formats changing what RTP even means.
Keeping the two numbers apart
So there are two numbers. One is the studio's published default — what spec sheets and this site's guides quote. The other is the value of the build actually open in front of you — usually printed in the in-game rules or info screen, and if it is not printed there, the honest reading is "unverifiable", not a guess.
A demo is a build too. Studio demos generally run the default configuration, but that is also something to confirm from the in-game label rather than assume.
Once the distinction sticks, the common confusion of "this RTP is listed differently elsewhere" mostly dissolves: the two documents were measuring different things, and usually neither is wrong.
Terms used here
- Configuration
- One of several builds of the same game at different RTPs — identical screen and rules, different payback setting.
- Default configuration
- The build a studio's spec sheet quotes. No deployment is guaranteed to be this build.
- In-game info screen
- Where the RTP of the build actually open is confirmed. If it is not printed there, the value stays unverified.