How We Test and Rate Online Slots

How we test slots: we play the free demo, log the features spin by spin, and rely on published Nolimit City figures rather than affiliate marketing claims.

How we test and score a slot

Every review here starts in the free demo, and every rating is a number from 0 to 10 that we can defend line by line. For San Quentin 2: Death Row we loaded the demo, played a couple of hundred spins, and logged the base game and the bonus separately. We verified the headline specs against the studio's own page: 96.13% default RTP, a 200,000x max win, "Insane" volatility, a 5x4 grid with 1,024 base ways, and a bet range of €0.20 to €100. Those are the numbers we build a score on, not the marketing round-ups.

We do not test on a live casino balance. A demo tells us how the game behaves; it does not tell us it is rigorous. So we flag our demo runs as small, unscientific samples and we never present a lucky or unlucky session as proof of anything.

What we log, spin by spin

The game's own history ledger records every bet, win and closing balance, so we can reconstruct a session rather than trust our memory. Across the San Quentin 2 demo we watched for a few specific things.

How often the base game paid at all, against the roughly 26.9% hit rate the databases report.
How long the dead stretches ran between bonuses, given the bonus triggers about once in 299 spins.
Whether the Enhancer Cells, xWays, Razor Split and Green Mile Spins behaved the way the official page describes them.
What the in-game bonus-buy panel actually charged, which is how we confirmed the Lucky Draw sits at 740x, not the 580x some affiliate copy prints.

How the number is set

We rate San Quentin 2 an 8.5 out of 10. A generous 200,000x ceiling and deep, layered mechanics push it up. The "Insane" variance, the reduced-RTP builds an operator can select, and the bonus buy being stripped in the UK pull it back down. Where outside aggregators land around 9 out of 10, we note that without naming them, and we keep our own figure separate from theirs.

What can move it

A score is not frozen. If Nolimit City republishes a spec, if a reduced-RTP build becomes the common one at casinos, or if our demo logging keeps contradicting a claim, we revise the review and the number. We would rather change a rating in public than defend a stale one, and we date what we change.

Which sources we trust, and in what order

Not every source carries the same weight, so we work down a hierarchy. At the top sits the provider's own material. Nolimit City's game page is where we take the confirmed figures for San Quentin 2, because the studio publishes the RTP, the max win, the volatility label and the feature set there before anyone else repeats it. When the game itself shows a number, like the bonus-buy panel pricing the Lucky Draw at 740x, that in-game reading beats any second-hand write-up.

Below the provider come structured databases and game-data aggregators. We use them to corroborate a spec and to surface the reduced-RTP builds, since operators can ship San Quentin 2 at 94.03%, 92.11% or 87.13% while only the 96.13% default appears on the official page. When a database and the studio agree, we treat the fact as confirmed. When they diverge, we quote the studio and note the gap.

Affiliate copy comes last, and we treat it as a lead to check rather than a source to cite. That is where the fabrications live: an "Electric Chair Event" that does not exist, xNudge borrowed from the original game, a rounded RTP, an invented volatility score. If a claim appears only in affiliate material and nowhere in the provider's page or a structured database, we either verify it in the demo ourselves or we label it as not confirmed. Ownership facts get the same treatment: we cite Evolution, the parent that completed the Nolimit City acquisition in 2022, not the studio that some copy names by mistake.

Getting it wrong, and fixing it

We will make mistakes. When we do, the fix is public and dated, and it takes priority over defending the original wording. If you spot an error in a spec, a feature description or a number, send it over and we will re-check it against the provider page and the demo before we correct the review.

Our Review Method: How We Test San Quentin 2