How we source our market data.

What this covers

Turbo Stars Market Intelligence is the data layer behind our published market research — the Turbo Lobby Index, the Slot RTP Benchmark, and the market statistics cited in our guides and glossary. This page describes where that data comes from, how it is verified, and the rules that decide what we will and will not publish. The method is public because the numbers are only as good as the reader's ability to interrogate them.

The two data layers

1. Catalog layer. A registry of 69,514 game builds from 1,370 studios, sourced from industry game feeds and stored as dated records: title, studio, release date, documented RTP, configurable-RTP flag, and game attributes. Of these, 54,355 builds carry a documented RTP that passes our validity rules.
2. Lobby layer. Automated monitoring of the live, public lobbies of 966 online casino brand websites. Each snapshot records which games each lobby shelves and at what position, section by section — 137,105 promoted placements in the August 2026 snapshot. Only publicly visible pages are observed; no accounts, deposits or gameplay are involved.

Most of our findings come from reading these layers against each other: what studios publish, versus what operators actually put in front of players.

Normalization

The same game and the same studio appear under many spellings across lobbies and feeds. Before any aggregation, every record is resolved to a canonical identity — one game, one slug; one studio, one canonical name — through a maintained alias registry. Aggregates are always computed over canonical identities, never raw labels, so a title's presence is not overstated by its spelling variants.

Verification and exclusion rules

• Validity bounds. Implausible values are excluded, not corrected — for example, RTP figures outside the 80–99.99% range are treated as feed errors and dropped from all statistics.
• No imputation. Where a lobby placement cannot be matched to a catalog build, it is excluded from cross-layer figures and the match rate is stated on the report. We do not estimate, extrapolate or fill gaps.
• Computed, not typed. Aggregates — medians, distributions, shares — are computed from the records at publication time, not maintained by hand.
• Documented values, honestly labeled. A "documented RTP" is the published or feed-supplied value of a build. For games with multiple certified configurations, the active value in any given casino may differ within the certified set — reports that touch configurable RTP say so explicitly, and the certification mechanics are described in our game certification entry.

What we never publish

• Individual casino brands. Lobby data appears only as aggregates across the monitored set. No report names, ranks or implies the identity of a specific operator brand.
• Client data. Figures from Turbo Stars' own commercial deployments — client revenues, conversions, project economics or client geographies — are not published in any form, aggregated or otherwise. Market reports are built from public observation, never from client systems.
• Commercial terms. Placement data describes public-facing visibility. It says nothing about deals, fees or agreements between operators and studios, and we do not present it as if it did.
• Unsourced numbers. A statistic appears in our content only with a first-party methodology behind it or a named, dated external source.

Freshness and corrections

Data stories are refreshed monthly; every edition states its snapshot month, and each report page carries its publication and modification dates in structured data. If an error is found, the figure is corrected on the page and the modification date updated — numbers are never silently rewritten without the date moving with them.

How to cite this data

Attribution format: "Turbo Stars Market Intelligence, [report name], [snapshot month]", linking the specific report page. Journalists and analysts can request underlying aggregates, charts or comment through our contact page — data requests are answered directly.