Faro Dorado — Free Slot With a Public RTP Audit
A five-reel slot that publishes its reel weights on the page, then runs four hundred thousand spins in the visitor’s own browser to check them. The figure beside the title was measured on the device you are reading this on.
Format: Slot · 5 reels × 3 rows · 5 fixed lines · Demonstrates: An RTP the reader can re-measure without leaving the page
Play it freeRun the audit yourself
The machine
| Reels | Five reels of twenty stops, three rows visible |
|---|---|
| Reel weights | 🍊×5 · 🌊×5 · ⚓×4 · ⭐×3 · 🪙×2 · WILD×1 — identical on every reel, published |
| Paylines | Five fixed — middle, top, bottom, V, inverted V |
| Stakes | 10 · 20 · 50 · 100 Gold Coins; pays scale, return does not |
| Basis of the figure | Measured, not enumerated — see below |
Why this one number is measured and the others are not
Five reels of twenty stops is 3.2 million distinct grids, and enumerating them inside a browser tab is not a reasonable thing to do to a visitor’s laptop. So Faro Dorado is the one game here whose return is sampled rather than solved: four hundred thousand spins run at load, and the audit button runs them again on demand.
That distinction matters more than the number. Eight of the twelve games on this platform have returns that are exactly computable, and those are stated without an error bar. This one is a measurement, so it is labelled as a measurement.
The figure was wrong once, and the audit is what caught it
Faro Dorado published 94.7% for part of 2026. A five-million-spin audit measured 92.38% — the paytable did not return what the label promised, and the label was the thing that was wrong. The paytable was re-solved to 94.646% and the published figure moved to 94.6%.
Nobody found that by reading the marketing. It was found by running the audit, which is the entire argument for shipping an audit button rather than a certificate. A certificate records that someone checked once; a button lets the reader check now.
The error and its correction are recorded in the project’s public error ledger, along with everything else that has gone wrong here.
The mathematics
Basis: measured. Sampled in your browser at page load and published with the interval that sample earned.
The reel strip is identical on all five reels — 🍊×5 · 🌊×5 · ⚓×4 · ⭐×3 · 🪙×2 · W×1 — and
this is what it pays.
| Symbol | Stops | 3 of a kind | 4 of a kind | 5 of a kind |
|---|---|---|---|---|
| 🍊 | 5/20 | 8× | 26× | 72× |
| 🌊 | 5/20 | 8× | 26× | 72× |
| ⚓ | 4/20 | 17× | 43× | 103× |
| ⭐ | 3/20 | 26× | 72× | 174× |
| 🪙 | 2/20 | 43× | 138× | 436× |
| WILD | 1/20 | 87× | 349× | 1743× |
Wins pay left to right on 5 fixed lines, and the wild substitutes for anything.
What “measured” costs you
400,000 spins run at page load. That sample is large enough to place
the return inside roughly ±0.72 points at 95% confidence — and that interval is computed from
the run’s own variance, not asserted. A measured figure published without its error bar invites
the reader to treat it as exact, which it is not.
Roughly 33% of spins return something. The 1743× five-wild line is the
reason the interval is as wide as it is: an outcome that rare and that large moves the average
around, and no sample size a browser can afford makes it disappear.
That width is also why the 92.38% audit described above was believable rather than dismissed as
a bad run: it sat far outside any interval 400,000 spins could produce. An error bar is not
decoration — it is what tells you whether a surprising measurement is noise or a fault.
What the gate does before the game loads
Nine states have enacted statutory bans on the sweepstakes casino model, and six more closed their markets by enforcement without passing anything. Every one of those instruments turns on redeemable value. This platform has none, so it stays lawful in all fifty — but the geo-gate still names the statute, because a compliance claim that cannot be checked against a citation is a marketing claim.
Select New Jersey and the gate blocks the lobby citing A5447/S4282. Select Oklahoma and it plays, with an amber banner recording that SB 1589 takes effect on 1 November 2026. The distinction between an enacted ban and a ban in force is the sort of thing operators discover late; here it is in the interface, fed by the same weekly-verified database as the state tracker.