Check whether an RTP statement covers a feature or the whole game
A percentage needs a defined scope: base play, a particular feature or an overall model may be different descriptions.
The distinction that matters
Read the text surrounding the RTP figure. If it explicitly limits the value to a mode or set of rules, keep that limitation attached. Do not combine a base-game figure and a feature figure by averaging them; the correct weighting would require their contribution to total turnover and return under a stated model.
A worked example
A fictional document gives one value for standard play and another for a separately priced feature. An unweighted mean ignores how often each is used and what each costs. The accurate worksheet has two scoped records until the documentation supplies a valid overall relationship.
Your next steps
- Record the exact mode named beside the value.
- Keep the cost basis with each mode.
- Do not average percentages without justified weights.
- Ask for clarification if the rules leave scope ambiguous.
Where this answer stops
This page does not endorse purchasing features or describe any operator's availability. A higher stated percentage alone cannot establish lower total expected expenditure when the price and turnover change.
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