RTP sources and calculation methods
Understand HighRTP’s source hierarchy, expected-loss formulas, sample limitations and the distinction between published returns and operator-specific evidence.
Updated 17 November 2026Keep three kinds of RTP information separate
A theoretical return describes a payout model under stated rules. A studio-published figure is evidence about the specified product, not automatically a confirmation of every operator’s deployment. Observed RTP describes the payouts and stakes of a completed sample. Each needs its own identity, scope and date.
A game’s active setting should be tied to the particular title, version, mode and operator. Where that evidence is unavailable, a general product figure should remain labelled as such. Player counts, turnover and public wallet transfers cannot independently establish an active RTP setting.
Source hierarchy and scope
For named product facts, prefer the studio’s own game page, rules or documented public interface. For jurisdictional requirements, use the relevant authority’s current provision rather than extending one country’s rules worldwide. For statistical methods, identify the mathematical assumptions and use an appropriate technical reference.
The source links in the guides identify the supporting document. Commercial documentation can establish what an implementation says it does; it is not independent evidence that every operator meets that description. A licence, a laboratory certificate and a seed proof also answer different questions. The evidence matrix sets out those boundaries.
The calculations used in worked examples
For a consistently defined stake basis, house edge = 100% − theoretical RTP. For fixed turnover, expected loss = total wagers × house-edge fraction. Theoretical RTP is the probability-weighted total payout divided by the full price of play. Observed RTP is completed payouts divided by completed wagers, multiplied by 100.
For example, $1,000 of fixed turnover at 96% RTP gives $40 expected loss. This is a mathematical expectation, not a promise that a particular player loses $40 or retains a specific balance. A budget may run out before the planned turnover is completed. Returned stakes must be counted consistently when converting profit odds into total payouts.
When combining sessions or games, add compatible monetary payouts and stakes rather than averaging unweighted percentages. Paid modes use the full amount charged, not just a nominal base bet. The calculation guide provides reproducible examples.
Statistical and public-data limitations
A measured return needs a complete and appropriately defined dataset. Payout variation, rare prizes, changing stakes, linked features, sample selection and the chosen stopping method can affect what an estimate supports. There is no universal number of spins that certifies every game.
Confidence intervals require assumptions appropriate to the observations. A precise-looking number without sample size, model and coverage is not a statistical audit. See sample-size methods and the UKGC’s operational monitoring guidance.
Public activity snapshots and wallet data have their own units and coverage. They should not be presented as a complete view of an operator’s liabilities, a solvency opinion or a forecast of the next game result. A retrieval timestamp describes when a source was read, not an independent certification.
What would substantiate an operator-specific verification claim?
Such a claim needs the operator, game, version, mode, date, relevant rules and a clear description of the check performed. A settlement allegation additionally needs matching round identifiers, full stakes and payouts. A testing claim needs the report’s product and scope.
These pages do not claim live testing on every real-money account, access to private certificates for every title, or a laboratory audit of the complete catalogue. The active-setting checklist helps readers identify the evidence needed for a concrete question.