The receipt is simple. Evolution Gaming sits on the Stockholm exchange as EVO.ST, runs roughly 1,500 live dealer tables, and clears about 20 billion rounds a month. Its published table-game RTP range is 96.00% to 99.00%. Its blackjack live table prints at 99.28%. European roulette prints at 97.30%. Those are the numbers, on the public record, sourced from Evolution's own game disclosures.
Playtech, the other name in the lawsuit headline, is listed in London as PTEC.L, headquartered in the Isle of Man, runs about 120 live tables and 600 RNG games, and publishes an RTP range of 94.00% to 97.50%. Two listed companies. Two audit panels (GLI plus iTech Labs on Playtech's side, GLI plus BMM plus eCOGRA on Evolution's). One defamation suit that an English-language reader was told would now include both. We pulled the procedural posture and found a gap between that headline and what the suit actually does.
What the Numbers Actually Say
Here is what we can establish from the documents we hold. Evolution is publicly listed and audited by three separate test labs. Playtech is publicly listed and audited by two. Both providers run on the same global English-market certification stack that the GLI public certificate registry hosts — and both publish RTP ranges in their marketing copy without specifying which audit lab signed off on which specific table.
That last point matters more than it reads. Evolution's blackjack RTP of 99.28% and its European roulette RTP of 97.30% are mathematical statements about the game's theoretical return. They are not statements about every deployed table at every operator that licenses Evolution's live studio feed. The certification scope — what was actually tested, on which build, against which paytable specification — sits inside the audit body's certificate, not on Evolution's marketing page.
The Egyptian-themed slot reader needs this distinction sharper than most. When you load Book of Ra Deluxe or Legacy of Dead at one operator and see 96.21% advertised, then load what looks like the identical game at another operator and see 94.10%, the difference is almost never the math. It is the build licensed to that specific operator. The certificate scope decides which build you are sitting on. The marketing copy almost never tells you which build that is.
So when a court refused Evolution's bid to fold Playtech into its defamation lawsuit, the procedural refusal does not change any of the math above. The two providers remain separately audited, separately listed, separately liable. The denial keeps the proceeding narrow. That is the actual receipt — narrowness, not vindication of either side.
For the live dealer reader who wants the Evolution game catalog page treated as authoritative, the published RTP range still holds. What the lawsuit posture changes is whether the cross-company discovery a wider suit would have produced will now happen in this proceeding. It will not.
What Nobody Mentions
The story the wire copy missed: a defamation suit between two listed game providers is a corporate-reputation proceeding, not a player-protection proceeding. Even if the suit had been expanded, the discovery would have surfaced internal communications about reputation, not the audit trail on any specific Book of Ra variant or any specific live blackjack build deployed at Bet365, PlayOJO, Royal Panda, Spin Casino, or the Entain brand stack that runs the Egyptian-themed slot libraries our MENA expat readers actually load.
The wider question — which audit lab certified which build at which RTP at which operator — is answered through certification body disclosure, not through one provider's litigation against another. The GLI certificate registry is the document that matters for a reader trying to verify a 96.5% RTP claim on a specific operator's Egyptian-themed slot lobby. The lawsuit posture is corporate noise.
Here is the second layer nobody surfaces. Evolution publishes one RTP range. Playtech publishes another. When an operator like Entain or Bet365 — both holding UKGC public-register licenses — markets a live dealer table or an Egyptian-themed slot to a customer, the operator chooses the build and the RTP variant from a menu of licensed configurations. The provider's published range is the range. The operator's deployed RTP is a single point inside it. The two are not the same statement and a reader who treats them as the same is going to be wrong frequently.
For Book of Ra, Book of Dead, Legacy of Dead, Eye of Horus — the four Egyptian-themed titles that pull MENA expat traffic — the published RTP range from the provider sits between roughly 94.00% and 96.70% depending on which provider and which variant. The operator-deployed RTP sits at one specific number inside that band. The certification body knows the number. The marketing page rarely does.
The defamation suit, denied expansion or otherwise, does not move any of this. That is what nobody mentions when the headline runs.
The Real Cost
Walk the math through and the cost of misreading a published RTP shows up fast. Take a hypothetical hour on a Book of Ra variant at the high end of the provider's stated range — 96.70% — versus the low end — 94.00%. On £1,000 of cumulative wagers across that hour, the expected loss at 96.70% is £33. At 94.00% it is £60. The gap is £27 per £1,000 wagered, or 81% more expected loss on the lower-RTP build. Same logo on the screen. Same theme. Different number, sourced from the same provider's licensed configuration menu.
This is the gap the Entain 2024 annual report does not break out — its £4,833m in 2024 revenue, with 88% from regulated markets, gets reported at the group level. The build-by-build RTP detail sits with the certification labs and the operator's own configuration management. In the public filings, neither Entain nor any other listed operator publishes the deployed RTP per slot variant per market. That is on the public record.
Flutter's investor results centre is the same posture. The 14.1m registered users and £11,790m in 2024 group revenue are disclosed at the consolidated level. The specific RTP of any single Egyptian-themed slot variant deployed at any FanDuel-adjacent or Sky Betting-adjacent brand is not in the annual report and never will be. The audit body holds that data. The litigation that the wire desks framed as a clarifying moment for the providers does nothing to surface it for the player.
A reader trying to convert provider-published RTP ranges into expected hourly cost on a specific deployed build needs three documents the marketing page does not give them: the operator's licensed configuration code, the certification body's most recent certificate for that build, and the operator's own published game info page (where it exists). The defamation proceeding, denied or otherwise, generates none of those three.
If You Only Remember One Thing
Evolution's bid to add Playtech to its defamation lawsuit was denied. The procedural narrowness of that denial does not validate either company's audit posture and does not change the published RTP math on any deployed game at any operator.
What it does is keep the public-record gap open. A reader who wants to know which audit lab certified which build of which Egyptian-themed slot at which RTP at which operator still has to walk the certificate registry, not the litigation docket. We would change our view if either provider published per-operator, per-build deployed RTP in their annual filings or if a regulator forced the disclosure. Until then, the marketing range is the range and the deployed build is a single point inside it.
FAQ
Did the court rule on Evolution's RTP claims or on Playtech's?
No. A denied procedural motion to add a defendant is a case-management decision, not a substantive ruling on either provider's published RTPs. Evolution's published table-game range remains 96.00%-99.00% with blackjack at 99.28% and European roulette at 97.30%. Playtech's published range remains 94.00%-97.50%. Both providers remain externally audited by GLI and their respective additional labs.
How does this affect the RTP of Book of Ra or Book of Dead at my preferred operator?
It does not. The deployed RTP on any specific Egyptian-themed slot variant is set by the operator's licensed configuration with the game provider and verified by the certification lab on file. A defamation proceeding between two providers does not change deployed build configurations. To verify your operator's specific build, the GLI public certificate registry and the operator's own game info page are the documents to read.
Why do the same Egyptian-themed slot titles show different RTPs at different operators?
Because game providers license a range of RTP variants for the same base game, and each operator deploys a specific build from that menu. A Book of Dead variant licensed at 96.21% at one UKGC-licensed brand and 94.21% at another is not a malfunction or an inconsistency — it is two distinct certified builds. The certification body holds the build-specific scope; the marketing copy almost never does.
Are Evolution and Playtech still both audited after the lawsuit?
Yes. Both companies remain publicly listed and externally audited. Evolution's audit panel includes GLI, BMM, and eCOGRA. Playtech's includes GLI and iTech Labs. The civil proceeding between them concerns alleged defamatory communications, not certification status. Neither company has had its audit credentials suspended or modified as a consequence of the litigation, and neither lab has withdrawn coverage.
Where do I verify the certification scope of a specific live dealer table?
The certification body's own register is the canonical document. GLI publishes certificates on its public resources page; iTech Labs and eCOGRA maintain equivalent registries. The certificate states the build version, paytable specification, RTP empirical validation methodology (typically multi-million simulated rounds), and the operator scope. Operator marketing pages summarise; the certificate is the source.
Does the UKGC track operator-level RTP disclosure on Egyptian-themed slots specifically?
Not at the title-by-title level in public filings. The UKGC public register confirms operator licensing status across roughly 268 online operators, and enforcement notices (when issued) detail conduct failures. Game-level RTP disclosure is governed by Licence Conditions and Codes of Practice and verified through the operator's certification arrangements, not through a UKGC-published per-title register.
Is there any regulator that publishes per-operator, per-build RTP for the games I play?
Not in the four English-speaking tier-one jurisdictions we track. The UKGC, MGA, NJDGE, and AGCO Ontario each require certification but do not maintain a public per-build RTP register accessible to retail players. Germany's GGL publishes cross-operator deposit and self-exclusion mechanics but not per-title RTP scope. The closest public artefact remains the certification body's certificate, where it has been made public.