How We Verify Slot Data

Every slot we review is loaded in a real browser, in the same free demo a player would open. Nothing is scraped from a listing page.

While the game loads, its client downloads a configuration from the provider's own game server. For many providers that configuration contains the paytable, the reel layout, the number of paylines or ways to win, and the bet limits — as structured data, sent to the game so it knows how to behave. Where we can read that configuration, it is our primary source, because it is the game telling us about itself.

Not every provider exposes a readable configuration. So we also navigate the game's own help, rules and paytable screens, capture them, and read the printed values from those captures.

Those captures are not thrown away. The screenshots published in the gallery on a review page are the same images the figures were read from, so the evidence sits next to the claim.

We apply a fixed order of precedence to every field:

• The game's own configuration — strongest, because it is what the game runs on.
• The provider's data feed — used where no configuration is readable.
• The in-game help screens — used for figures that appear nowhere else, such as descriptions of how a bonus round triggers.

This matters because the sources genuinely disagree. Comparing the two channels across a sample of games, the feed and the game contradicted each other on the payline count for a third of them — and the game was right every time. One title listed in the feed with 10 paylines reports 5 to its own client.

We record which channel won each field, per game, and show it on the page.

On every slot review, the specification row carries a small marker:

• verified — read directly from the game's own configuration.
• in-game — read from the game's help or paytable screens.
• provider — supplied by the provider's feed and not yet confirmed inside the game.

Below the specifications we state the date the game was last opened and read. A figure with no marker is one we have not yet confirmed ourselves, and we would rather say nothing than imply a verification that did not happen.

Where we hold the paytable as data, we publish it as a table of multipliers alongside the screenshot it came from.

• We do not estimate RTP by simulating spins. We publish the figure the game itself reports, or nothing.
• We do not convert payout multipliers into cash figures. A multiplier is what the game states; a money amount would depend on a stake we cannot know, and these are free demo games.
• We do not fill gaps with plausible-looking numbers. Coverage of the strongest source varies by provider, and where we do not have a figure the page simply does not show one.