ToolsGambling
TG
/rtp / changelog

RTP Change Tracker

Every weekly diff — stated RTP changes, new slots, removed slots, variant updates, coverage shifts — across 15 providers. Source-backed, timestamped, citable.

Total changes
101
This month
55
RTP changes
1
New slots
78
⚠ Biggest change tracked2026-05-18
Gonzo's Quest Megaways
Red Tiger · RTP change
98.16%95.77%-2.39pp
Filter:

What's in this feed

We track six change types: stated RTP changed, native RTP variants updated, slot added or removed from a provider's catalog, new provider integrated, and provider coverage status reclassified (complete / partial / exhausted_public).

A new entry appears here only when the weekly cron detects a meaningful diff: ≥0.5% of slots changed RTP, any new variant detected, ≥25 net new slots, ≥50 metadata improvements, or any provider/coverage change. Smaller drift is logged in the run report but not committed to the public feed — keeps the changelog signal-rich.

Programmatic consumers: hit /api/rtp/history for the JSON feed (filter by type, slot, provider, or since). Cron schedule: every Monday 06:00 UTC.

How this RTP tracker works

Weekly monitored snapshots

Every Monday at 06:00 UTC we re-scan all 15 providers, compare the new dataset to the previous frozen version, and append only meaningful changes to the public feed.

Signal-rich diffs, not noise

Minor page drift stays in internal run logs. This public changelog focuses on events editors and players can actually cite: RTP changes, new variants, new slots, removed slots, and coverage updates.

Source-backed and reviewable

Each release is tied to provider pages, timestamps, and versioned registry data. That makes the feed useful not just for browsing, but for journalism, audits, and historical verification.

Why RTP changes matter

For players and casino reviewers

A slot can keep the same name while its published RTP or available variants change over time. Tracking those moves helps explain why an older review, bonus guide, or casino comparison may no longer match the latest provider data.

For researchers and affiliate editors

A structured changelog creates a citation trail. Instead of saying a provider "sometimes changes RTP", you can point to dated entries, provider clusters, and annual archives built from the same registry.

Provider coverage in this feed

These are the providers with the most recorded activity in the changelog so far.

Read methodology →
BGaming
38 changes
Verified weekly
Microgaming
27 changes
Verified weekly
Yggdrasil
12 changes
Verified weekly
Play'n GO
10 changes
Verified weekly
Pragmatic Play
4 changes
Verified weekly
Red Tiger
3 changes
Verified weekly
Wazdan
2 changes
Verified weekly
Thunderkick
2 changes
Verified weekly
Nolimit City
1 changes
Verified weekly
Endorphina
1 changes
Verified weekly
First recorded
2026-05-09
Last updated
2026-06-22
Total changes
101
Refresh cadence
Weekly

Latest tracked changes

Showing entries 26–50 of 101. Older history stays accessible through pagination.

Page 2 / 5
  1. June 2026

  2. NEW SLOT2026-06-22v1.0.1
  3. NEW SLOT2026-06-22v1.0.1
  4. NEW SLOT2026-06-22v1.0.1
    Reel of Ra· BGaming
    RTP: 97.02%
  5. NEW SLOT2026-06-22v1.0.1
  6. NEW SLOT2026-06-22v1.0.1
  7. NEW SLOT2026-06-22v1.0.1
  8. NEW SLOT2026-06-22v1.0.1
  9. NEW SLOT2026-06-22v1.0.1
    Wild Blood 2· Play'n GO
    RTP: 96.18%
  10. REMOVED2026-06-22v1.0.1
    Bling Blitz Diamond Drop· BGaming
  11. REMOVED2026-06-22v1.0.1
    Chicken Shot· BGaming
  12. REMOVED2026-06-22v1.0.1
    Derby Rush· BGaming
  13. REMOVED2026-06-22v1.0.1
    Elements of Power· BGaming
  14. REMOVED2026-06-22v1.0.1
    Fishing Club 2· BGaming
  15. REMOVED2026-06-22v1.0.1
    Fishing Time· BGaming
  16. REMOVED2026-06-22v1.0.1
    Gemhalla Xtreme· BGaming
  17. REMOVED2026-06-22v1.0.1
    Golden Ticket· Play'n GO
  18. REMOVED2026-06-22v1.0.1
    Grand Buffalo Hold and Win· BGaming
  19. REMOVED2026-06-22v1.0.1
    HOT ROCKET 5x 3x 2x· BGaming
  20. REMOVED2026-06-22v1.0.1
    Kicker Mania· BGaming
  21. REMOVED2026-06-22v1.0.1
    Lucky Pack: 2026 Cup· BGaming
  22. REMOVED2026-06-22v1.0.1
    Money Maker· BGaming
  23. REMOVED2026-06-22v1.0.1
    Penalty Duel with Júlio César· BGaming
  24. REMOVED2026-06-22v1.0.1
    Royal Easter· BGaming
26–50 / 101

What RTP change tracking means for slot reviewers

RTP is not a static spec sheet number. A provider can roll out a new game build, swap the default variant a casino is allowed to deploy, or quietly retire a slot from the public catalog. Each of those moves shows up here as a dated entry in the Slot RTP Registry, with the source URL and snapshot hash that captured it.

The feed is rebuilt from a frozen snapshot every Monday at 06:00 UTC. The diff engine flags meaningful drift only — half-percent RTP shifts, brand-new variant tiers, twenty-five or more net new slots from a provider, or a coverage reclassification. The exact thresholds and confidence model live in the methodology. Older runs are available in the 2026 archive.

If you write slot reviews, build a comparison tool, or run a player community, this feed is meant to be cited. It works alongside the best RTP rankings and the biggest variant ranges so a single dated entry tells the full story: what changed, when we saw it, and which provider page proves it.

FAQ

How often does the changelog update?
The feed updates after the weekly cron run every Monday at 06:00 UTC. If a provider page changes in a meaningful way, the new diff appears here automatically.
What counts as a meaningful RTP change?
We publish entries for stated RTP changes, native RTP variant updates, slot additions or removals, new provider integrations, and provider coverage reclassifications. Small cosmetic drift does not create public feed entries.
Why is this page paginated instead of one endless feed?
Pagination keeps the changelog usable as the archive grows into hundreds of entries. It also preserves crawlable URLs for older pages instead of hiding history behind client-only infinite scroll.
Can I filter to RTP-only updates?
Yes. Use the filter buttons at the top of the page to switch between all changes, RTP-only changes, new slots, and removed slots. Provider-specific archives also have dedicated URLs.
Is there a machine-readable version of this feed?
Yes. The same data powers /api/rtp/history, which supports filters like type, provider, since, until, limit, and offset.
Why link out to provider-specific changelog pages?
Provider pages reduce noise for readers who only care about one catalog, such as Pragmatic Play or NetEnt. They also build a cleaner archive structure than creating thousands of thin per-slot history pages.
Why does the RTP change for a slot?
Providers ship multiple math models for the same game and let the operator pick which version to deploy. When a provider updates the default version, retires an older build, or publishes a new RTP tier, the headline number on their page changes. We pick that up on the next weekly run. See the methodology for how we read provider pages.
How often do providers actually change RTP?
It varies. A few providers push variant updates quarterly when they renegotiate operator contracts. Most leave a slot's published RTP untouched for years. Looking at the per-provider columns on this page shows which catalogs see the most movement and which stay flat.
Can a casino offer a different RTP version of the same slot?
Yes, this is the whole reason native RTP variants exist. The same slot at one casino may run a 96% build while another casino runs a 91% build of the exact same game. The provider publishes the menu of available variants and the operator chooses. Casinos under UK regulation must disclose the live variant on the rules page. Most do not unless asked.
How do you verify the RTP history is accurate?
Every observation is content-addressed with a sha256 of the full HTML snapshot at fetch time. We keep the snapshot for as long as the registry exists, so any past RTP claim can be replayed against the page we actually read. The full provenance chain is documented in methodology.