RTP Pillar·Chapter 2

How RTP is calculated

Three methods compute a game’s return: exhaustive enumeration, analytic combinatorics and Monte-Carlo simulation. A public worked example takes enumeration to full depth; the honest addition is the confidence interval those examples skip.

By Vadym Zelinskyiverified 2026-09-18Current · 100%

Because theoretical RTP is a property of the design rather than of any play session, it can be computed before a single round is played. There are three standard ways to do it, and they are complementary rather than competing. GLI-11 recognises this directly: it defines theoretical return as based on “mathematical calculations or simulations”.

Method 1 — exhaustive enumeration

The most direct method lists every possible outcome, multiplies each payout by its probability, and sums. For a game small enough, this gives the exact RTP with no estimation at all.

A toy one-reel game with 10 equally likely stops, staking 1 unit per spin: one stop pays 5, two stops pay 1, the other seven pay nothing. Expected return = (1×5 + 2×1 + 7×0) / 10 = 7 / 10 = 0.70, i.e. an RTP of 70% and a house edge of 30%. That is the whole calculation — no play required, no secret needed.

Real slots are larger, but not beyond enumeration. A widely cited public worked example — the Atkins Diet analysis on Wizard of Odds — takes exactly this route to full depth: five reels of 32 stops give 32⁵ = 33,554,432 combinations, and a program with “five nested loops that tallied the total for each win for each possible combination” sums them to an RTP of 97.046% (63.460% from line pays, 6.976% from scatters, 26.610% from the bonus). It is a designer’s own teaching game rather than a commercial title, but it settles a common myth: the full mathematics of a slot can be laid out publicly, in the open, symbol by symbol.

Method 2 — analytic combinatorics

Enumeration becomes wasteful when structure can be exploited. Instead of walking 33 million rows, you can compute the probability of each winning pattern in closed form — from symbol weights, line definitions and the combinatorics of how symbols land — and combine them. Analytic methods give the same exact answer as enumeration, faster, and they scale to games where listing every row would be pointless. Where a game’s outcome space is finite and well-structured, an exact number is always obtainable in principle; the choice between enumeration and combinatorics is one of convenience.

Method 3 — Monte-Carlo, and the interval the examples skip

Some modern games resist exact methods: deep free-spin recursion, cascading wins, symbol collection and re-trigger chains can make the exact outcome space astronomically large. Here designers estimate the return by simulation — play the game’s model against its own random source for a very large number of rounds and average the results.

A simulated RTP is an estimate, and the honest version of it always carries a confidence interval. If the per-round return has standard deviation σ and you simulate N rounds, the standard error of the estimated mean is σ / √N, and a 95% interval is roughly the estimate ± 1.96 σ / √N. This is the layer most public examples stop short of: they report a point estimate and move on. It also runs the other way — fixing the interval you want and solving for N tells you how many rounds a claim of “96.0%” actually requires, which is the entire subject of how RTP is verified.

What practitioners actually use

In studios the methods are used side by side: an exact analytic model where it is tractable, simulation for the parts that are not, and cross-checks between the two. That the industry builds dedicated tooling for it at all is itself telling — a commercial slot-math product, Slot Designer (Game Design Automation Pty Ltd), markets itself on “complementing Excel” and reducing “maths errors and rework,” which is a fair description of the real workflow: spreadsheets for the tractable model, purpose-built tools and simulation for everything past it. (That is a vendor’s own description of its product, cited as evidence of practice, not endorsed.)

Which method wins, and when

Small or well-structured game → enumerate or solve it exactly; there is no reason to accept estimation error you can avoid. Large or recursive game → simulate, and report the confidence interval honestly. In every case the answer is a design fact, not a measurement of your luck. See the return-to-player concept in the game-math spine, where a live simulator lets you watch estimated return settle toward its true value, and the wider set of probability explorables in the Lab.

Common questions

Can you actually calculate a slot’s RTP without playing it?

Yes. RTP is a property of the game’s design — its reels, symbol weights and pay table — so it can be computed directly. For small games you enumerate every outcome; for larger ones you use combinatorial shortcuts or Monte-Carlo simulation. A public worked example (the Atkins Diet slot) enumerates all 33,554,432 outcomes to reach 97.046% exactly, which shows the maths is neither secret nor brute-force-only.

When do you have to simulate instead of calculating exactly?

When exact enumeration is infeasible — deep bonus recursions, re-spins, or cascading mechanics whose outcome space is astronomically large. Simulation estimates the return from a large random sample instead, and its estimate comes with a confidence interval that shrinks as the sample grows. GLI-11 accepts both routes: it defines theoretical RTP as based on “mathematical calculations or simulations”.

Sources (3)

Education, not advice. This chapter explains how return-to-player is defined, computed and checked so you can read the number honestly. It is not a system, and nothing here treats gambling as a way to make money — over enough play the mathematics favours the house. 18+.

Next in the pathHow RTP is verified