RTP Change Tracker
Every weekly diff — stated RTP changes, new slots, removed slots, variant updates, coverage shifts — across 15 providers. Source-backed, timestamped, citable.
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.
Latest tracked changes
Showing entries 51–75 of 101. Older history stays accessible through pagination.
June 2026
- REMOVED2026-06-22v1.0.1Royal Roulette 500X· BGaming
- REMOVED2026-06-22v1.0.1Shark and Spark Hold and Win· BGaming
- REMOVED2026-06-22v1.0.1Sparky and Shortz· Play'n GO
- REMOVED2026-06-22v1.0.1Super Wheel· Play'n GO
- REMOVED2026-06-22v1.0.1Ultras· BGaming
May 2026
- RTP CHANGED2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
- NEW SLOT2026-05-18v1.0.1
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?▸
What counts as a meaningful RTP change?▸
Why is this page paginated instead of one endless feed?▸
Can I filter to RTP-only updates?▸
Is there a machine-readable version of this feed?▸
type, provider, since, until, limit, and offset.