Stakelogic pays £122,835 after a manual stopwatch missed 16 UK slot games running too fast
The UK regulator says Tiger Temple 88 ran a cycle in 1.97 seconds and a wider retest found another 15 games below the 2.5-second minimum.
Jump to a section
16 games · 1.97-second cycle
Milliseconds cannot be certified reliably with a manual stopwatch
Great Britain · Slot testing
Evidence behind the story
What we checked
Primary documents
3 checked
Response record
Response included
Last source check
26 August 2026
Next scheduled review
2 September 2026
Why this matters
The settlement turns a timing rule into a quality-control lesson: a manual stopwatch missed millisecond-level failures across 16 games, and the first fix did not trigger an immediate portfolio review.
Procedural status
Regulatory settlement concluded
Stakelogic agreed to a £122,835 payment in lieu of a financial penalty, publication and investigation costs. No criminal case or licence suspension was announced.
The current picture
- Stakelogic agreed to a £122,835 payment in lieu of a financial penalty after breaching the UK's 2.5-second slot-cycle standard.
- Tiger Temple 88 ran at 1.97 seconds and a portfolio retest found another 15 non-compliant games.
- The regulator says the supplier relied on a manual stopwatch to test small timing intervals.
Confirmed by the record
- Stakelogic reported the Tiger Temple 88 issue to the Gambling Commission after correcting it.
- Tiger Temple 88 was non-compliant from 28 to 30 May 2025.
- The other 15 games were available during different periods between 31 October 2021 and 30 October 2025.
- Stakelogic disabled all games available to the Great Britain market after the wider scope became clear.
Not established
- The public statement does not quantify player losses or identify a customer harmed by the faster cycles.
- The Commission does not name the licensed operator websites that carried the games.
- The £122,835 is a regulatory-settlement payment in lieu of a financial penalty, not a criminal fine.
- The record does not say that every Stakelogic game was non-compliant.
Sources for each key claim
Evidence map
Each core claim is paired with the document used to substantiate it. Open the record and check our reading.
Stakelogic agreed to pay £122,835 after 16 games breached the 2.5-second cycle minimum.
Tiger Temple 88 ran at 1.97 seconds and another 15 games failed the wider review.
The supplier used a manual stopwatch and later disabled and retested its Great Britain portfolio.
One game exposed a wider testing failure
Stakelogic agreed to pay £122,835 after the UK Gambling Commission found that 16 slot games had run faster than the minimum cycle time allowed in Great Britain. The first confirmed game was Tiger Temple 88, which allowed a new cycle after 1.97 seconds instead of waiting at least 2.5 seconds.
The supplier reported that issue after correcting it. Commission enquiries then led Stakelogic to retest its entire Great Britain portfolio, where another 15 games fell below the same technical standard. The case expanded from one title to a quality-assurance problem.
The test used a manual stopwatch
The most unusual detail is the measurement method. The public statement says Stakelogic used a manual stopwatch to check small timing intervals. The Commission called that practice open to significant inaccuracy and found the supplier's testing and incident-management controls below the expected standard.
A stopwatch may look adequate for a rough demonstration. It is poorly suited to verifying differences measured in milliseconds across a software portfolio. Human reaction time becomes part of the test, and a repeatable technical rule turns into a subjective observation.
How fast the games were
Tiger Temple 88 was 0.53 seconds below the 2.5-second minimum. Across the other 15 games, the shortfall ranged from 0.001 to 0.675 seconds. The regulator says many of those titles were 42 milliseconds or less below the requirement.
Those smaller deviations still counted as breaches. The standard sets a minimum, not a tolerance band that suppliers can interpret informally. The range also explains why a manual test could miss problems that automated measurement should capture consistently.
The first response was too narrow
Stakelogic discovered the Tiger Temple 88 issue on 28 May 2025 but kept the game live until a fix was deployed on 30 May. The Commission treated the failure to suspend it immediately as an aggravating factor. It also criticised the delay before the supplier reviewed all Great Britain games tested with the same method.
Once the wider scope was understood, the company disabled every game it offered in the market while the issue was addressed. It also cooperated with the investigation, supplied information on time and accepted the failures early. Those actions appear in the regulator's mitigation record.
Why Britain requires a 2.5-second gap
The minimum slot-cycle time was introduced in October 2021 as part of rules intended to reduce the intensity of online play. A new game cycle must not begin until at least 2.5 seconds after the previous one starts, and the player must take a fresh action to continue.
The rule is about product behaviour, not only how a game is described. Even a small configuration or measurement error can change the number of wagering opportunities available during a session. That is why the technical test and the production result both matter.
What the settlement does and does not say
The £122,835 payment is in lieu of a financial penalty and forms part of a concluded regulatory settlement. Stakelogic also agreed to publication of the facts and to pay the Commission's investigation costs. The record does not announce a criminal case or a licence suspension.
It also does not quantify how many people played the affected games or identify a player loss caused by the timing. The verified story is narrower and more useful: 16 non-compliant titles, a manual testing method, delayed portfolio escalation and a settlement after the supplier disabled and retested its Great Britain games.
The control should be reproducible
A supplier testing a hard timing threshold should produce the same result repeatedly across environments and releases. Automated measurements can preserve the interval, log the test and flag a failure before release. A person pressing a stopwatch cannot offer the same audit trail at millisecond scale.
The wider lesson is about escalation. Once one title failed a shared test method, every game certified by that method became relevant. The settlement shows why incident procedures must connect a local defect to the larger population that may share its cause.
Response record
The settlement record includes Stakelogic's self-report, game suspension, cooperation, early acceptance and planned testing and incident-management changes.
Status: included