Titles can exist at several return settings. A precise copied percentage without provider documentation and version context remains weak evidence.
The missing signal
A long-run percentage for one build is not a short-session promise, legality certificate or universal game fact.
Precision can be theatrical. Before trusting a number or seal, ask who produced it, which entity or version it covers, the date it describes and which denominator or comparison has been left out.
A repeatable three-step test
- Write the claim plainly. Remove adjectives and keep the exact proposition.
- Match the source. Prefer the regulator, provider rule file or complete contract responsible for that fact.
- Keep the boundary. Do not extend one case, screenshot or configuration to the entire service.
Attach source, edition and active setting to every RTP number.
What it cannot establish
Strong evidence about one mechanic does not establish operator legality, payment reliability or suitability. Product, entity, transaction and jurisdiction questions should remain separate until a source explicitly connects them.