Our Testing Method for a Slot in Full

Where testing happens

The developer's own free demo, every time

Scoring scale

1 to 10, across 5 named criteria for a game verdict

Evidence accepted

Recorded session, the game's own rules document, a downloadable register

Sessions on record

1, of 80 paid spins across one evening

Known limits

4, each printed on the page it affects

Audience

Adults aged 18 or over

Demo Play Comes First in Our Testing

Demo play comes before every other step, so testing starts in the current official client instead of on a marketing page. We load the demo, note the play-money balance of 5,000.00 it grants, then run a recorded session at a bet held fixed throughout.

Nothing is skipped. Every spin in a session goes into the written record. Each line goes down while the screen is still open.

That written record is what later turns into a score. The demo runs the build the maker ships for deployment, launch switches and all, so it exposes the paytable, the settings panel and the feature behaviour, while the stake stays imaginary; what can differ between the two is the licence configuration the client is handed at launch. Adults aged 18 years or over can open it without an account.

In Short, Before You Trust a Testing Score

Here's what a score on this site is worth: it's the product of one recorded play-money run plus a pile of documents, and nothing else. We've never deposited at a casino for this site at all, and you'll see that limit repeated wherever it matters.

That limit is deliberate, and it is stated on every page. A demo can't measure the psychology of real money, so the score speaks to mechanics, licensing and sourcing, while the return figure stays the maker's own claim rather than something we measured.

A session record lists the bet, the running balance after each spin and the final result. It is the only evidence that stands behind a sentence beginning with “in our testing”. The Pirots 5 free demo page shows how a reader can repeat the same run without an account.

What Should a Reader Check Before You Start?

Four checks are worth making before you weigh a score, and each one is available without an account. Page through the paytable first, then compare the rules screen against what the maker publishes on its game page.

1. Open the demo and read the rules screen to its end, where the return figures sit.
2. Read the maker's own page for the game and note that it prints no return figure at all.
3. Change the stake and watch what the cap is worth in money, which settles what the advertised headline means.
4. Check which return your own casino publishes before you deposit anything.

That is the same build, launch configuration included, so a reader needs a few minutes and no money at all for the check. Doing the four in advance is the fastest way to test this method instead of trusting it, and every page here carries the date of its own last check.

What Demo Testing Cannot Show

Demo testing has a ceiling, and this is the honest shape of it. A run of 80 paid spins is far too few to say anything about a long-run return, so the published figure does that job instead.

Our run closed 2.65 down across 80 paid spins at a 1.00 bet, and its best single result was 42.30, or 42.3 times the bet. Against the 96.0% the build we played prints for itself, a result like that over a run this short is ordinary. Those are observations, not statistics, and the page says so wherever they appear.

One number from that run is worth printing on its own, and it is a zero. Across all 80 paid spins, not one paid anything by itself: every unit that came back arrived through the birds finishing a collect, which is exactly what the rules describe and a very different experience from a game that trickles.

Why a Single Spin Cannot Be Checked

This is where the method runs out of road, and saying so is more useful than dressing it up. A game of this kind exposes no server seed, no player seed and no published hash, so there is nothing a reader could hash together and compare. A spin is a result you take on trust or walk away from.

A certified generator and a title-level certificate are two different assurances, and only the first of them exists here. The rules screen states that the game runs on a certified random number generator and stops there: no certificate, number or audit date is published for this title, and none of the laboratories keeps a public per-title register a reader could search. Nothing on this title is offered as provably fair, and no page here claims otherwise: the maker says the game runs on a certified generator, which is an assurance a reader takes on trust rather than a proof they can recompute.

What a Reader Is Left With

What is left is an audit a reader has to take on trust, which is weaker than a proof they could run themselves. The gap gets printed as a gap rather than smoothed over.

So the two assurances appear side by side instead of merged, and the checks we can actually run take their place. The paytable, the rules text, the bet grid and the licence registers are all open to anyone, and every one of them is repeatable in an afternoon.

Sourced Numbers Quoted as Printed

The method below is written for a player in United Kingdom, and that choice decides which register answers and which stays silent. Every number is sourced before it is printed, and the date of its check travels with it. Returns, bet limits and licence details come only from the client, the studio rules document or a regulator register, and each figure keeps the shape they gave it.

The game prints one return for an ordinary spin on its own rules screen, and a casino may still run a different build of it, because the figure belongs to the deployment rather than to the title. Those two statements describe different things, so the pages keep them apart rather than blending them into one average.

The same sourcing rule governs the win side. The rules screen caps a round at 10,000 times the bet, the promotional screen in the same client turns that into a headline of a million, and the two agree only because the headline assumes the maximum stake. Each figure travels with the screen that printed it instead of being merged. We invent no payment methods, bonuses, licences or multipliers, and the return reference page is the model for this rule.

Honest Cons from the Recorded Session

Every page names its downsides. Cons are mandatory on every page that carries a verdict. A testing round that comes back with only good news was never a test, so the drawbacks are written before the verdict.

Every page carrying a verdict includes a real downsides section and, where it applies, a named alternative the editors would pick instead.

The drawbacks stay specific: a maker that publishes no return, no volatility and no hit frequency on its own page for the game, odds of the advertised ceiling that the rules template has a line for and this build never prints, five build configurations between 96% and 87% with nothing outside a casino to say which one it runs, and a free demo assembled on Maltese settings rather than British ones. We also name who should avoid the game, and that warning sits before the sponsored button instead of after it.

Scoring: 5 Named Criteria, and What a Score Cannot Mean

A game verdict rests on 5 named criteria and runs from 1 to 10: the return figure, licence and certification, the feature, the bet grid and ceiling, and the disclosure behind every number. A score of 7 or higher means the analyst would open the demo again.

What a score here cannot mean is that a casino is good or bad. A second scale exists for that, 16 criteria across trust, the game and money, computed from a casino dossier rather than from an opinion, and on this site it grades nothing, because no casino dossier was built. A reader therefore gets a graded game and an ungraded market, which is the honest shape of what was actually read.

What the Client and the Registers Provide

The studio provides the demo client, and its rules screen carries the return figure, the win cap and the symbol descriptions in plain text. Demo mode supports play money only, so nothing you hold is ever at stake.

The registers supply the licence half of the same picture, and on this game two of them answer by name. Great Britain publishes a downloadable file of every licensed gambling business and this supplier is in it, under account 40844; Malta would confirm the authorisation the maker prints in its own footer, but its register answers no search we could run; Great Britain and Sweden both answer, and both carry the supplier under its own account. So the Maltese line stays a footer claim, and the page says which register was opened and what it returned.

Volatility the studio does not settle, and here it does not state it at all: neither its page for the game nor the rules screen carries a word or a number for it, and the grades in circulation are catalogue opinions. The one frequency the game does report, a hit frequency of 26.11%, comes from the launch configuration rather than from anything the maker publishes.

Which Criteria Decide a Score?

Our criteria are fixed before a game is opened, and they stay fixed whatever the result turns out to be. To verify a claim, the editors go back to the document that carries it, then quote the wording they find there rather than their impression of it.

Every page includes the source beside the figure it carries. Readers can follow the same trail, so they can open a document themselves, and you can disagree with a score while still trusting the numbers under it.

Which Lines the Player Never Sees

The rules the client loads are a template, and the game server fills the gaps at launch. Some of those gaps are filled and printed; others are filled and then switched off. The table keeps the two apart, because the difference is the whole story.

What Else the Client States Outright

Four more fields come off the client screens, copied exactly as they appear, and two of them record that the client states nothing at all. Nothing in the table is inferred from a third party.

Why There Are No Casino Pages Here

No casino is written up on this site, and that is a decision rather than an omission. A casino page under this method needs its own dossier: the licence number read out of its footer, looked up in a register, then every figure it publishes about this title recorded as found. No such dossier was built for this game. So no page here reports what any particular casino shows, charges or allows.

The checklist below is what such a dossier would have to carry. It is printed here so a reader can see the bar, and so the absence of casino pages reads as a standard we did not meet rather than a gap we hid. Aggregator claims stay out, and a casino whose presence we could not prove gets no page here, which on this game means every casino.

How Licence Regulation Is Confirmed

Regulation is confirmed by register instead of by badge, and on this game the register answers. Great Britain publishes a downloadable file of every licensed gambling business, and the maker of this game is in it: Elkab Studios AB, account 40844, licence 040844-R-320591-019, Active, carrying Gambling Software since 19 March 2015. Sweden answers too, listing the same company for game software until 30 June 2028. What that means is narrow and worth stating narrowly: the supplier is licensed in both places, which says nothing about any particular casino.

One category error is worth heading off, because it is common and it is wrong. Several markets license operators and keep no public register of game studios at all — Italy's concession list names concessionaires rather than suppliers — so a supplier cannot be looked up there and that regulator publishes no number to quote. Any page claiming a verified Italian supplier licence for this developer is describing a document that is not published.

• Account number and holder, read in the regulator's register on the test date.
• Presence of this title in the lobby, proved by a catalogue sitemap, a lobby record or an indexed game page.
• The wagering contribution for this game, read in the operator's own bonus terms rather than in a banner.
• Demo availability, where the operator states it in a form a reader can check.
• Payment methods and identity-check rules, taken from the operator help pages.

Every page here says not confirmed wherever a figure resisted verification, and not published wherever nobody prints it at all. That wording is deliberate, because a gap a reader can see beats a number nobody can trace.

Terms This Method Uses

Recorded session

A demo run written down spin by spin, with the bet, the running balance and the outcome of each one.

Certified generator

A random number generator audited by an outside laboratory, and the only fairness assurance this title offers, since no spin here can be recomputed.

Return configuration

A licence setting sent to the client at launch, which decides which lines of the rules screen a player is shown; the odds of the ceiling and the bet range are switched off in the build we played.

Account number

The number a regulator files a licensed business under, and the key a supplier claim is looked up in a published register, as this game's supplier can be in Great Britain and Sweden.

What the Record Actually Holds

The record is one run in the developer's own demo, written down as it happened, never a deposit. The closing figure only means something beside the press count, which is exactly why the page prints both.

4 Types of Testing Limit, Compared

The complete list of testing limits runs to four entries, and each one shapes every score here. Readers who weigh a verdict should read them before the verdict itself.

Does a Demo Spin Prove Anything?

A demo spin proves the mechanics and stops there; a long-run average comes out of the maker's model instead. That is why the return figure is quoted from the maker instead of measured here.

Readers can repeat any of it themselves in a few minutes. They will meet the same paytable, the same settings panel and the same feature our sessions recorded.

Recap: The 4 Limits of This Testing Method

Four limits shape this testing method, and the page names each out loud. Testing happens in the demo instead of with real money, so nothing here describes a deposit or a withdrawal. Eighty paid spins say nothing reliable about a long run, which is why the return figure stays the maker's claim rather than our measurement. A spin cannot be recomputed by anyone, so fairness is reported rather than proved. And no casino was read at all for this game, so nothing here describes what one shows, charges or allows.

Everything else on this page recaps in a sentence or two. Demo play comes first, the fairness gap is named rather than papered over, sourced numbers are quoted as printed, cons sit beside the verdict, a game verdict rests on 5 named criteria while the operator instrument weighs 16 and runs on nothing here, and a supplier is looked up in a register file rather than taken off a footer. All testing is done by the analyst who signs each page, and every page here is written for adults aged 18 or over.