Slot RTP Benchmarks by Provider 2026: Reference Table

Published slot RTP defaults cluster between 95.0% and 96.7% across the major studios, but the figure an operator actually runs is a configuration choice rather than a fixed property of the game. Several providers ship the same title in four or more certified RTP versions, and the operator selects which build goes live. That single fact is the reason a provider-level RTP table is a range rather than a number, and it is why game margin, GGR, NGR, and affiliate payouts all move when a portfolio manager changes a supplier default. This page is the reference layer: published ranges by provider, which studios document multiple RTP versions, verified values for named flagship titles, and the regulatory minimums that bound the whole exercise. It is operator-facing portfolio and margin analysis, reviewed quarterly.

Why Provider RTP Is a Range and Not a Number

Four RTP bands account for most multi-version releases: roughly 96.x%, 94.x%, 92.x%, and 88.x%, with documented floors near 84% at Play'n GO and Nolimit City. A studio certifies each band as a separate build, the aggregator or remote game server exposes them as selectable configurations, and the operator picks one per market or per brand. Nothing about the game's mechanics changes: the same paylines or ways to win, the same bonus round, the same max win multiplier. What changes is the theoretical return, and therefore the house edge, the long-run game margin, and the shape of the player experience that follows from a lower expected return at the same volatility.

Hacksaw Gaming provides the clearest primary evidence, publishing all four bands as a single string on its own game pages. BGaming states the practice directly, describing how providers release several RTP versions of the same game and the casino selects the one matching its margin targets or commercial terms. Amusnet demonstrates it in its catalogue, where titles in the same brand family sit at materially different published RTPs. Operators should treat a supplier's headline RTP as the top of a range until the contract or the RGS configuration screen says otherwise.

RTP Benchmarks by Provider: The Reference Table

Published RTP defaults for the studios below run from about 88% on legacy jackpot titles to 98% on individual high-return outliers, with the working cluster between 95.0% and 96.7%. The table records what each provider or its official game pages publish, whether multiple certified RTP versions of the same title are documented, the studio's volatility positioning, and one verified named title with its default RTP. Where a claim could not be traced to a primary source, the cell says so rather than carrying an estimate.

Providers That Do Not Publish Portfolio-Level RTP

Portfolio-level RTP is a disclosure choice rather than an industry standard, and the 14 studios below decline it: they publish RTP only on individual game pages, in certification documents, or behind operator portals, which means no defensible portfolio-level range exists for them in public sources. That is not a quality signal. It reflects a straightforward commercial choice: a studio that ships configurable bands has little reason to publish a single portfolio figure that its operator customers will not all be running. For these suppliers, the RTP configuration in play should be read from the certification records and the RGS configuration screen during integration, not inferred from a marketing page.

Named Flagship Titles: Verified RTP Reference

Gates of Olympus runs a 96.50% default RTP on Pragmatic Play's own published game page, and the titles below are listed with the same standard: provider-published values are marked as such, and values sourced from secondary game databases are marked separately so a reader can weight them accordingly. These are the titles that appear most often in portfolio conversations, benchmark decks, and supplier negotiations, which makes a single verified list more useful than a larger unverified one.

Regulatory Minimums and Disclosure Rules by Jurisdiction

Malta lowered its minimum RTP from 92% to 85% in 2021 under the MGA Player Protection Directive, which set the floor most offshore-facing configuration decisions still work against. The wider picture is inconsistent by design: some regulators set a numeric floor, some mandate disclosure, and several do neither. The UK Gambling Commission sets no minimum RTP and its technical standard accepts a game description, the house edge, the RTP percentage, or the probability of winning as sufficient information, which means an operator can satisfy the rule without publishing an RTP figure at all. Italy's ADM sets a 90% minimum for fixed-odds games including slots. In the United States the floors are far lower and long-standing: Nevada requires a 75% minimum theoretical payout per wager, New Jersey at least 83%.

Certification is the control that makes any of this auditable. Each RTP band is a separately tested build, and independent test houses such as GLI issue the RNG and game certificates that regulators rely on. When an operator disputes what a supplier configured, the certification record and the RGS configuration log are the evidence, not the marketing page. Portfolio managers should keep both accessible per market, because a configuration that is compliant in one licence can breach the floor in another.

What an RTP Band Does to Game Margin, GGR, and NGR

A move from 96% to 94% RTP raises theoretical game margin from 4% to 6%, a 50% increase in GGR per unit of turnover, and that single relationship is the whole commercial argument. House edge is simply 100% minus RTP, so GGR equals turnover multiplied by the house edge. Because NGR is GGR after bonuses, payment fees, gaming taxes, and platform and content fees, a higher game margin flows through to NGR at whatever ratio the market's tax and bonus load allows, typically leaving 55% to 75% of the incremental GGR. Affiliate payouts move with it: a RevShare partner on NGR earns more per unit of turnover under a lower RTP configuration, while a CPA partner earns nothing extra and simply sees the operator's return on each acquired player improve.

The counterweight is player lifetime value. A lower configured return shortens sessions at the same stake and volatility, which raises churn and reduces the retention that makes a cohort profitable over months rather than weeks. The margin gain is immediate and measurable; the lifetime value loss is delayed and shows up in cohort curves a quarter later, which is precisely why RTP reductions look better in a monthly margin review than they do in an annual one. Any portfolio decision here should be evaluated on cohort revenue over at least 90 days, not on game margin in the first reporting period.

The 2026 UK Duty Rise and the Market RTP Response

UK Remote Gaming Duty rose from 21% to 40% of GGR on April 1, 2026, and trade coverage since has reported operators responding by moving standard slot RTP from around 96% toward 94%, with 92% cited as the floor requested in some supplier negotiations. The arithmetic is straightforward: a 19 point duty increase removes roughly a fifth of GGR from the NGR line, and reconfiguring the portfolio down two RTP points restores gross margin without touching acquisition spend. Not every operator has taken that route. Hollywoodbets UK has publicly positioned on consistently selecting the highest available RTP versions, treating configured return as a differentiator rather than a lever.

For affiliate programs the second-order effect is what matters. Partners on NGR-based RevShare in the UK saw their commission base compressed by the duty change itself, then partially restored by portfolio reconfiguration, which makes year-on-year partner performance comparisons across the April 2026 boundary meaningless without adjusting for both. Programs that did not carry an explicit change-in-law clause left partners absorbing the duty increase, and programs that reconfigured RTP without telling partners created a second, quieter change in the same commission base. Documenting both is the difference between a defensible statement and a dispute.

How Operators Should Evaluate an RTP Configuration Decision

Operators should evaluate RTP configuration as a portfolio decision with a compliance floor, a margin case, and a retention cost, in that order. Treating it as a pure margin lever produces a predictable pattern: a strong first quarter, a weakening cohort curve, and a slow migration of high-value players to competitors running higher configured returns in the same market. The sequence below is the working checklist, and every step of it should leave an auditable record, because the configuration in force at any date is exactly what a regulator, a supplier, or an affiliate partner will later ask about.

1. Establish the regulatory floor for every market the brand is licensed in, and confirm the configured band clears the strictest applicable minimum rather than the average.
2. Read the actual configured RTP per title from the RGS configuration and the certification record, not from the supplier's marketing page or a third-party database.
3. Model the margin case at portfolio level using turnover weighted by title, because a two point change on 5% of turnover is not a portfolio decision.
4. Model the retention cost against cohort revenue over at least 90 days, so the lifetime value effect is visible alongside the immediate game margin gain.
5. Check the responsible gambling implications of a lower configured return for the player segments most exposed to it, and document the assessment.
6. Recalculate affiliate exposure: NGR-based RevShare payouts move with configured RTP, and partner statements should reconcile to the configuration actually in force during the period.
7. Record the change with its effective date per market and per title, so partner disputes and regulatory queries resolve against evidence rather than recollection.

How to Use and Cite This Page

Two rules keep citations of this reference accurate. Cite the RTP figure together with its source class, because a provider-published default and a secondary-database value carry different weight and this page labels every entry accordingly. Attach the as-of date, because configured RTP is a live operator setting rather than a fixed property of a game: the same title can run at 96.38% with one operator and 88.42% with another on the same day, and both are correct.

Methodology, Sources & Update Cadence

Three source classes back this page, and they are labelled rather than blended. Provider-published values come from the studios' own game pages and are marked as provider published. Secondary values come from established game databases and are marked as such, because they are compiled rather than authoritative. Regulatory rules come from the regulators' own published standards and directives, including MGA player protection requirements, UK Gambling Commission licence conditions and technical standards, Italy's ADM framework, and Germany's GGL product rules. Where a provider does not publish a portfolio-level range, the table says so rather than estimating one, and 14 studios appear in that category.

Two source types are deliberately excluded. Community-tracked return figures from third-party slot trackers are observed returns from limited samples, not published RTP, and are unusable for commercial modelling. Affiliate summary pages that recycle identical RTP band claims across unrelated domains without a primary source were rejected outright, which is why multi-version RTP is marked unconfirmed for several large studios where secondary sources assert it confidently. Market context on the 2026 UK duty change and the operator response draws on trade reporting from iGaming Business and SBC News, with European market data from EGBA. Margin arithmetic is Track360 analysis and uses round illustrative turnover figures.

Last updated July 18, 2026. This reference is reviewed quarterly (January, April, July, October), with out-of-cycle updates when a regulator changes a minimum RTP or disclosure rule, or when a major studio publishes portfolio-level RTP data for the first time. Corrections are welcome, and providers who publish a verifiable portfolio-level RTP range are invited to submit it with a link to the primary source; verified submissions move a row out of the unconfirmed table in the following review cycle.

RTP is not a property of a game, it is a setting on a portfolio. The number a supplier publishes is the top of a range, and the number an operator runs is a commercial decision that shows up in game margin this month and in cohort retention two quarters from now.