Method
This page describes how we collect, check and display values for inferno slots. You can see which sources we use, which fields are published per slot, and how lists and medians are calculated. We also explain the limits of these data and how updates and corrections are handled.
Sources and checks
Data directly from game data and catalogues
We publish data sheets and calculated overviews of inferno slots. The values come from provider game data and structured catalogue scans. Each slot is checked for fields such as RTP, volatility, max win, hit frequency, bet range, layout, ways, release date, features and themes.
The data are verified up to and including June 17, 2026. Where available, we link studio technical documentation to the database fields. When sources differ, the most recent and formally published game configuration takes precedence. If a field is not unambiguous, we do not publish it and mark it internally for recheck. Corrections are logged and propagated to all relevant lists.
Which fields we show
Core parameters per slot
Per slot we show RTP, volatility, max win, hit frequency, bet range, layout, ways, release date, features and theme. For RTP we use the published value. If a slot has multiple RTP versions, we show the RTP value from the game data and note that versions exist; whether that is the highest version is not in our data.
We do not show a range: for multiple RTP versions there is one value with a note that versions exist. Volatility is shown on the provider’s scale or, if that scale is absent, as a text label from the documentation. Max win is the maximum theoretical payout according to the game rules. Layout and ways describe the symbol matrix and win methods. Fields that are not available are omitted.
Calculations and lists
Selection by rules, sorting by columns
Lists and hubs are generated from the full pool of inferno slots with database coverage. The pool contains 171 titles that meet the theme criteria. Selection uses fixed filters on theme, feature and provider. We then sort by one column, for example RTP, max win or release date.
Medians and other summaries are calculated directly from the stored values. No overview ranks quality; it only shows data according to the chosen sorting. Counts in lists, and also aggregates, are always calculated by the database and never filled in manually.
Limits of the data
What the figures do and do not show
RTP is a long‑term average over very many spins and not a prediction for an individual sequence. Max win is a theoretical ceiling and not an expectation. Volatility is a relative indication from the game data.
If a field is missing in the source, we omit it rather than estimate it. For slots with multiple RTP versions we show one value from the game data; which version that is, is not in our data, and in a specific environment a different version may be active. Our data describe configurations and publications, not outcomes or probabilities in concrete circumstances.
Updates and corrections
Regular recheck of fields
We refresh the dataset periodically when providers adjust documentation, new inferno slots are added or existing fields change. Possible errors are compared with the game data and corrected where needed.
Changes flow through to data sheets, hubs and lists. When RTP versions change we adjust the entry and note the date of the check in the internal log.
