Microgaming's published RTP range across its slot library is 95.00% to 97.00%. Tomb Raider, the 2004 Eidos-licensed five-reel title built on the original Microgaming Viper platform, sits at the bottom of that band when served at 95.7%. It also sits below that band — at 94.5% — when served through certain operator contracts. The published range, on the public record, does not contemplate the 94.5% configuration. We have read the standard coverage of this game's RTP across the English-language casino web. None of it walks back to why the same Microgaming binary ships in two tiers, or which contractual variable flips the switch.
What Every Article on Tomb Raider's RTP Gets Wrong
The standard write-up of Tomb Raider's RTP reads like a paraphrase of a marketing one-pager. A single number is cited — almost always 95.7%. That number is attached to the game as if it were a property of the binary. The article then moves on to bonus features, paylines, and where to play. RTP is treated as a fact about Lara Croft. It is not. RTP is a fact about a contract between Microgaming and the operator deploying the game.
The first error is the conflation of Microgaming's library-wide published RTP range with the per-deployment certified output of a specific title. Microgaming publishes a band of 95.00% to 97.00% across roughly 800 games. That figure, on the public record at Gaming Laboratories International, is a ceiling-and-floor description for the studio's catalog. It is not a per-game guarantee. It is not a per-deployment guarantee. The 94.5% configuration of Tomb Raider sits below the published floor, which means the published floor is either inaccurate as a description of the live catalog or is silently excluding lower-tier deployments. The standard coverage never registers the contradiction.
The second error is treating the iTech Labs and eCOGRA audit certificates as a stamp on the game. They are not. The certificates document statistical randomness of the RNG seed and the empirical RTP of the specific game math configuration tested in the lab. When Microgaming ships the same Tomb Raider executable with a different math file — a different paytable seed — to a different operator, that is a different deployment. A different deployment is, in audit terms, a different scope. The certificate the affiliate-mill article links to almost never matches the deployment the reader is actually about to play.
The third error is omitting the operator entirely. The conventional article will state "Tomb Raider's RTP is 95.7%." It will not say which operator. It will not say which jurisdiction. It will not name the license tier the operator holds with Microgaming. The reader is left with a number that floats in space, attached to a game and not to a deployment.
The pattern across the entire conventional coverage is the same: surface-level retrieval of a published number, no walk-back to the document that produced the number, no acknowledgment of the operator-contract layer that actually decides what the player receives.
What Is Almost Always Missing From the 95.7% vs 94.5% Discussion
What never appears in the conventional coverage is the commercial mechanism that produces the two tiers in the first place. Microgaming, as a B2B content supplier, sells games to operators on a wholesale basis. The wholesale contract specifies an RTP tier. The operator selects from a set of available configurations at the point of license. Same executable, different paytable file, different deployed RTP.
The economics are not hidden — they are simply never written about. A 1.2 percentage-point gap between tiers translates, at scale, into operator gross margin. On a slot turning over £100m in annual wagers, the gap between 95.7% and 94.5% is £1.2m in retained operator gross win. That margin is the variable being optimized when an operator selects the lower tier. It does not appear on the player-facing info screen. It does not appear in the affiliate write-up. It would appear only inside the wholesale licensing terms, and those terms are private contracts. They are not on the public record at all.
Second, the regulatory overlay is missing. UKGC-licensed operators are required to display the deployed RTP on the game's info screen. Other Tier 1 jurisdictions have variable rules — the AGCO Ontario framework, on the public record at iGaming Ontario, lists 49 licensed operators with disclosure requirements that diverge from UKGC's. The German GGL framework, documented at gluecksspiel-behoerde.de, enforces a different transparency regime built around the cross-operator deposit cap of 1,000 EUR per month and a centralized OASIS exclusion register. Same Tomb Raider game file. Four jurisdictions. Four different disclosure surfaces. The conventional coverage segments none of it.
Third, almost universally missing: the audit certificate version. Microgaming's RNG and game-math configurations are tested by iTech Labs and eCOGRA, and these certificates expire. A re-certification can carry a different deployed configuration than the prior cert. The affiliate-mill page that screenshots a certificate from 2019 may be pointing at a scope that no longer matches the live deployment in 2026. The published range across the NetEnt catalog, by way of comparison on the public record at netent.com, runs from 94.00% to 96.70% — and NetEnt, like Microgaming, ships the same titles in operator-tiered configurations. The B2B tier mechanism is industry-standard. The coverage is industry-blind to it.
What is missing, in aggregate, is the entire commercial and regulatory layer that determines which RTP the player actually receives when the reels stop.
What I Would Say Instead: The Operator Contract Decides the Tier
The Tomb Raider RTP question is not a question about Tomb Raider. It is a question about which operator's contract with Microgaming the player happens to be inside of when the reels spin. The game file is the same. The math configuration loaded onto that file is different. The variable that flips the switch is the operator's wholesale licensing tier — chosen at the point of integration, paid for in operator margin, and largely invisible to the player.
Run the cost reality check. A modest recreational player at £2 per spin, 400 spins per session, two sessions per week, over 50 weeks, wagers £80,000 a year through Tomb Raider. The delta between the 95.7% tier and the 94.5% tier on that volume is £960 in expected annual loss. Add the cost of currency conversion if the player is a MENA expat funding in AED through a Skrill or Neteller route, the cost of any deposit-method fee, and the opportunity cost of capital tied up in playthrough requirements on attached bonuses. The realistic annual delta for a player who sits on the wrong side of the contract lands closer to £1,100. That is the price of the tier the operator selected at the moment of integration. The player paid it without ever being shown that a choice existed.
This is where the conventional framing breaks down. The reader does not need a paragraph on volatility classification or bonus features. The reader needs to be told: check the operator's in-game info screen for the deployed RTP figure on this specific title; if the screen displays 94.5%, the operator selected the lower tier; if it displays 95.7%, they selected the upper one. The decision is documented at the operator level, not the game level. The decision is downstream of a private B2B contract that neither the affiliate site nor the player has ever seen.
The operator selection logic is rational. A Spin Casino or Royal Panda running aggressive new-player acquisition has different unit economics than a mature Entain brand like Ladbrokes or Coral cross-selling into a 28m-customer base, on the public record at Entain's 2024 Annual Report. Different unit economics produce different tier selections. PlayOJO, which positions itself on no-wagering promotions, has stated incentives to deploy higher-tier RTPs because the marketing premise depends on a transparent return-to-player floor. Bet365, on its UKGC-licensed deployment, displays the deployed RTP on each game's info screen because the enforcement risk for misstating it is material. The 2022 Hillside (Bet365) settlement was £582,120, on the public record at the UKGC public register, and that is on the smaller end of the enforcement scale — Ladbrokes and Coral paid £17m in the same period for adjacent disclosure and AML failures.
Watch three things. One: the in-game info screen at the operator you are about to play at — that is the only RTP figure binding to your specific session, and it is the figure a regulator can enforce against. Two: the certification date stamped on the game footer — anything older than 24 months in 2026 deserves a question to support before you fund. Three: whether the operator has begun publishing wholesale-tier disclosures alongside per-game RTP figures, a transparency move that some MGA and AGCO licensees are starting to make voluntarily, and that signals where the disclosure ratchet is heading on the public record.
FAQ
Is the 95.7% or the 94.5% RTP the "correct" Tomb Raider figure?
Neither is more correct than the other. Both are valid deployed configurations of the same Microgaming game file, each selected by a specific operator at the wholesale contract layer. The player-binding figure is the one displayed on the in-game info screen at the operator they are funded on. Citing "the RTP of Tomb Raider" without naming the operator and jurisdiction is meaningless — the number floats free of the contract that produced it.
How do I check which tier my operator is serving?
On UKGC-licensed deployments, the deployed RTP is required to be visible on the game's info screen, typically reached through the in-game menu or settings cog. Outside UKGC, disclosure is variable — Ontario's AGCO regime requires it, the German GGL regime requires it, and Maltese MGA deployments increasingly include it voluntarily. If the info screen displays no RTP figure, treat that absence as an answer in itself and ask support before funding.
Why isn't the 94.5% configuration inside Microgaming's published 95.00%–97.00% range?
That is precisely the disclosure gap we are surfacing in the piece. The published range describes the studio's catalog ceiling and floor but does not appear to contemplate every shipped tier. Either the range is being maintained as an aspirational statement of higher-tier deployments only, or the lower-tier configurations are being treated as out-of-scope for the published band. Either reading exposes the same point: the range is a catalog claim, not a per-deployment guarantee.
Does any regulator force operators to disclose the tier they selected?
Disclosure of the deployed RTP — what the player receives — is mandated by UKGC, AGCO Ontario, and the German GGL framework. Disclosure of the wholesale tier the operator paid for is mandated by none of them. The commercial layer remains opaque by design. Operators who voluntarily publish wholesale tiers alongside deployed RTP are doing so as a marketing differentiation move, not as a compliance requirement.
Does the same tier-selection mechanism apply to other Microgaming slots?
Yes. The B2B wholesale model is studio-wide, not title-specific. Mega Moolah, Immortal Romance, Thunderstruck II, and the rest of the Microgaming catalog all ship in operator-selectable RTP configurations. The published library range of 95.00%–97.00% is a band across the catalog. The deployed figure for any specific title at any specific operator can sit above, within, or below that band depending on the contract.
Can the deployed RTP change after I create my account at an operator?
In principle, yes — operators can re-tier games at contract renewal points or during major platform updates. UKGC-licensed operators are required to surface the change on the info screen and may be required to notify materially affected players, depending on the change's scope. In practice, mid-contract re-tiering is uncommon because of the integration and audit cost. The certification date in the game footer is the most reliable signal that a configuration is current.