Public registry of 3,646 slots from 15 providers. Stated RTP, native variants, weekly source snapshots — every entry traceable to a provider URL. Free to embed with attribution. methodology
3,646 tracked3,646 with verified RTPmulti-variant: 70715 providers
Start here
Three steps. Click any card to begin.
Verified evidence
Live data for Sweet Bonanza — every claim above the fold has a source URL behind it. Click to verify yourself.
Every record in the registry carries the same provenance: source URL, sha256 content snapshot, verification timestamp. Auditable from your laptop in 10 seconds.
What you can do with the Slot RTP Database
Four use-case clusters built for slot reviewers, casino comparison editors, and data engineers.
Slot RTP database — browse and search
Public registry of 3,646 provider-stated RTP values across 15 providers. Native variant ranges, volatility, max-win, release year — every entry traceable to a source URL with weekly verification snapshots.
For: top-N RTP roundups, provider comparison pages, factual reference in any slot review.
One-line iframe embed per slot. Auto-updates weekly from the same registry — no maintenance on your side. Light/dark themes, customizable accent color, optional white-label removal of attribution on paid tier.
Pick 2-3 slots from the registry, get an auto-built comparison table with Markdown, HTML, and Schema.org JSON-LD outputs — plus a single iframe that renders all selected slots together for embedding.
For: X vs Y articles, top-3 RTP roundups, variant comparison pieces, provider-vs-provider analysis.
Programmatic access via /api/rtp/list and /api/rtp/. Public JSON, CORS-enabled, CC-BY 4.0 license. 1000 requests/day per IP, no signup required. Schema.org Dataset markup discoverable via Google Dataset Search.
Pick a slot → get a ready-made citation, paragraph, disclaimer, and embed code in 60 seconds. Built for: slot reviews, top-N RTP roundups, comparison articles, sticky sidebars.
Pick a style → customize → copy widget + Schema.org snippet. Done in 60 seconds.
What you actually get when you embed this widget
1. Free Schema.org Dataset + Product markup
Most slot reviews score poorly on E-E-A-T because they quote RTP without source citations. Our widget ships a copy-paste JSON-LD snippet — paste it in your page <head> alongside the iframe. Google reads it as Dataset + Product structured data attached to your URL.
2. Your own casino referral link in the widget
Optional <Affiliate URL> + <Label> turns the widget into a CTA for your casino partner. No revenue share — we don't take a cut. Click goes straight to your tracking link with rel="sponsored nofollow" (correct per Google guidelines).
3. Auto-updating data you never maintain
Weekly Monday cron re-scrapes all 15 providers. RTP changes propagate to every embed automatically — you don't refresh anything. Each record carries source_url + sha256 snapshot hash, so the citation is auditable.
4. Verified trust signals visible to readers
Each widget shows a Verified pill + last-refresh date + tracked-since timestamp. Readers see at a glance that the data is current. Stable for the last N weeks = signal of provider reliability.
5. Free with a tiny attribution
Free tier: small "data: toolsgambling.com" link in the widget footer (one inbound link to us per embed). Pro tier (manual issuance — DM): white-label, no attribution, custom domain. No signup, no Stripe, no friction for the free tier.
How the registry works
What we track.
Every entry is a real slot from one of 15 production providers (Pragmatic Play, NetEnt, Play’n GO, Yggdrasil, BGaming and 10 others). For each slot we store stated RTP, native RTP variants when the provider publishes them, volatility, max win, release year, and source URL. 707 slots have multiple RTP variants published by the provider — that’s the data point you won’t find anywhere else.
Where data comes from.
We scrape each provider’s public website, store a content snapshot (sha256 hash) for every record, and refresh weekly via cron. No regulator data — regulators don’t publish per-slot RTP. We track what providers themselves publish, which is the same source any other site has access to. See methodology for the full provenance chain.
How to use this page.
Search or filter by provider/game type below. Click any row to expand the slot panel with full data, an embed generator, and a shareable deep link. Want to embed the widget on your site? See how to embed. Track when RTP changes? Watch the changelog.
Why this database exists
Slot RTP is fragmented and hard to verify.
Provider-published RTP sits across 15+ provider websites, each with its own format. Casino help pages show a different RTP again — the value the operator licensed for that specific install. Affiliate sites quote numbers without source citations. Journalists writing about gambling math have no canonical place to verify a claim.
Provider-published RTP is the trust anchor.
It's the value the provider declares to regulators and casinos. Different operators may license different variants (e.g. 96.5% / 94.5% / 92.0% for the same game), but the provider's published value is the audited reference. Tracking it cleanly, with snapshot evidence, is what makes downstream comparison possible.
This registry solves that.
One database. One source per record. One canonical URL for citation. Free to embed with attribution, free to query via API, weekly-refreshed via cron — no manual edit-then-deploy loop.
What makes this database different
Source provenance
Every record carries a source_url + snapshot_id (sha256 hash of the scraped HTML at fetch time) + last_verified. 270 MB of raw HTML evidence stored. Verifiable, not vibes.
Native variant tracking
707 slots with 2–7 RTP variants the provider explicitly publishes (Play'n GO publishes 5 variants per slot, Yggdrasil publishes ranges). Most registries flatten this to a single number — we don't.
Weekly cron + meaningful diff
Mondays 06:00 UTC, all 15 providers re-scraped. Six trigger criteria detect material change (≥0.5% RTP shift, any new variant, ≥25 new slots, coverage status changes, etc.). Public changelog auto-fills. /rtp/changelog
CC-BY 4.0 license
All data licensed CC-BY 4.0. Reusable for journalism, research, commercial integration — with attribution. Schema.org Dataset markup makes it indexable in Google Dataset Search.
Free embeddable widget
Free for affiliate sites, blogs, casino reviews — three sizes, three themes, custom accent color. Iframe embed, no setup. Each embed gets a dofollow link back to the registry. how to embed
Open API, free tier
Public JSON API, 1,000 requests / 24h per IP, no signup required. Pro tier (early access via email) for higher quota. API docs
Legal language — copy as-is for regulatory disclosures
▾
RTP is provider-stated and represents long-run expected return, not single-session result. Casinos may install regional or operator-specific variants; check the slot's info page in your casino client for the live value.
Schema.org JSON-LD
For technical editors — paste into your page <head>
Pre-written text if you need shortcuts (citation, paragraph, multi-format)
▾
One-sentence citation
Dragon's Luck has a stated RTP of 96.24%, source-verified by ToolsGambling on May 11, 2026.
Editorial paragraph
Red Tiger's Dragon's Luck carries a stated Return-to-Player of 96.24%, verified against the provider's own catalogue page on May 11, 2026. The RTP figure represents long-run mathematical expectation, not session-level outcome. Source URL and snapshot evidence are available for citation.
Output formats
For article body (plain text)
Dragon's Luck (Red Tiger) — RTP 96.24%, verified by ToolsGambling on May 11, 2026. Source: redtiger.com
For Markdown / Ghost / Notion
**Dragon's Luck** (Red Tiger) — RTP **96.24%**, verified by [ToolsGambling](https://toolsgambling.com/rtp?slot=dragons-luck) on May 11, 2026. Source: [redtiger.com](https://redtiger.com/games/dragons-luck)
+Schema.org snippet for your page (Google reads this) SEO bonus▾
Paste this <script type="application/ld+json"> in your page <head> alongside the iframe. Google indexes it as Dataset + Product structured data attached to your URL — free SEO signal for your slot review.
Paste in <head>, body, or near the widget. Anywhere on the page works for Google.
+Add your casino affiliate link (optional) Revenue▾
Renders a "Play at →" button inside the widget. Click goes to your tracking URL. No revenue share with us. Configure rel attribute for your affiliate setup (direct link or cloaked redirect).
Recommended: direct affiliate link. Google's preferred 'sponsored' marker (combined with nofollow).
Only https:// URLs accepted. Label max 60 chars. Cloaked redirects (your-site.com/go/casino) work — pick 'none' to keep your own SEO control.
Embeds include a small "data: toolsgambling.com" link in the widget footer. This is a required attribution for the free tier — it's how others discover the registry. Pro tier removes it.
RTP (Return to Player) is the percentage of wagered money a slot pays back to players over millions of spins. A slot with 96.50% RTP returns $96.50 per $100 wagered on average over the long run. Higher RTP = lower house edge. RTP doesn't guarantee outcomes for any single session — it's a long-run statistical property.
Where does the data in this registry come from?▸
Every record comes from the provider's own public game-info pages — pragmaticplay.com, netent.com, playngo.com, etc. Our scrapers fetch the page, extract the published RTP/variants/volatility, and store a sha256 snapshot of the HTML at fetch time. Full methodology.
How often is the data updated?▸
Weekly automated cron runs every Monday at 06:00 UTC. All 15 providers re-scraped, diff detected against previous frozen dataset, public release committed when changes are meaningful. Sub-week edits via GitHub Actions manual trigger when needed.
Why don't all slots have volatility / max win / hit frequency?▸
Many providers don't publish those fields publicly. We never invent data — if a field is missing, it shows as —. Currently 77% have volatility, 28% have max win, 19% have hit frequency. Per-field coverage is documented in methodology.
What's the difference between stated RTP and casino-configured RTP?▸
Providers publish a "stated RTP" — the value declared to regulators and certified by gaming labs. Casinos can sometimes license different RTP variants (e.g. 96.5% / 94.5% / 92.0% for the same game) and configure their install accordingly. We track the provider-stated value as the trust anchor. Per-casino variant tracking is on the roadmap (Q3 2026).
Can I trust this for journalism or research?▸
Yes. Every record carries provenance: source_url, snapshot_id (sha256 of scraped HTML), last_verified timestamp. Schema.org Dataset markup makes the registry indexable in Google Dataset Search. Licensed under CC-BY 4.0 — citation-grade.
How do I cite this database?▸
Recommended citation: ToolsGambling Slot RTP Registry, v1.0.0, https://toolsgambling.com/rtp. For specific slots, link to https://toolsgambling.com/rtp?slot=<canonical-slug>. Include the access date — we record last_verified timestamps you can quote alongside.
Is the embed widget really free? What's the catch?▸
Yes, free for all use cases — affiliate sites, blogs, journalism, internal tools, commercial. The widget includes a small attribution link back to toolsgambling.com/rtp in the footer (dofollow). Pro tier (early access via email) removes attribution + raises API quota. How to embed.
What's the API rate limit?▸
1,000 requests / 24h per IP, anonymous, no signup required. Headers X-RateLimit-Limit / X-RateLimit-Remaining / X-RateLimit-Reset on every response. For higher quota or commercial use cases, email hello@toolsgambling.com for early-access keys.
How do I report an incorrect RTP value?▸
Email hello@toolsgambling.com with the slot slug + provider + the value you believe is correct + the URL where the provider publishes it. We'll re-verify against the provider's page within 24h. Our snapshot of the page is always available for audit.
When will per-casino RTP variants be available?▸
Q3 2026. Top-5 UK-licensed casinos seeded manually first (LeoVegas, Bet365, Videoslots, 888, William Hill), then automated weekly cron with UK residential proxy infrastructure. Will surface inside the widget as "available at N casinos · RTP range X–Y%".
What does "multi-variant" mean? Why is it a separate count?▸
707 slots have multiple RTP variants explicitly published by the provider. For example, Play'n GO's Moon Princess has 5 published variants: 84.50% / 87.50% / 91.49% / 94.51% / 96.50%. Single-variant slots have one declared value. Multi-variant tracking is rare — most registries flatten to one number per slot. We don't.
Maintained by Evgeniy Volkov · Every record carries a source_url + sha256 snapshot hash. See methodology for the full provenance chain, or the about page for who runs this and why.