Why a published RTP range is not one confirmed value
A range can describe multiple configurations or uncertainty. Its midpoint is not automatically the configuration you are using.
The distinction that matters
Keep a range as a range and record what the source says it represents. Do not select its highest endpoint for a headline or average the endpoints to create a precise-looking figure. A calculation using a range can show scenarios, provided the result remains explicitly conditional.
A worked example
An illustrative document lists 94% to 96%. On C$1,000 turnover, those assumptions imply expected costs of C$60 and C$40 respectively. The midpoint gives C$50 at 95%, but that does not prove a 95% configuration exists or applies. The two endpoint calculations are clearer than an invented certainty.
Your next steps
- Record the meaning of the range if stated.
- Ask which value applies to the exact version.
- Label any endpoint calculations as scenarios.
- Avoid ranking an unconfirmed range against a confirmed single configuration.
Where this answer stops
The example uses hypothetical percentages. Neither the midpoint nor an endpoint is a prediction of personal losses. Do not use the range as a reason to increase play or test which value seems to fit a short session.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction