28 Jun 2026
Stakelogic BV Settles Regulatory Matter With UK Gambling Commission Over Spin Time Standards

The UK Gambling Commission has confirmed that software provider Stakelogic BV agreed to a regulatory settlement of £122,835 following breaches of minimum spin time requirements on multiple slots titles, and the matter came to light through a combination of the company's own reporting and subsequent investigation by the regulator.
Under the Remote Technical Standards, specifically RTS 14 which addresses responsible product design, games must maintain a minimum interval of 2.5 seconds between spins to support safer play mechanics, and this requirement applies across all licensed operators and their suppliers in the British market.
Details of the Identified Breaches
One title, Tiger Temple 88, operated outside the required interval for a limited window during May 2025 while fifteen additional games did so across scattered periods stretching from 2021 through 2025, and the commission's published statement makes clear that the deviations stemmed from inaccurate manual stopwatch testing methods used during internal quality checks.
Because the testing relied on manual timing rather than automated verification systems, certain builds released to the market did not consistently meet the 2.5-second threshold, and once the discrepancies were detected the provider took immediate steps to remove the affected titles from active distribution.
Company Response and Corrective Measures
Stakelogic BV self-suspended the non-compliant games upon discovery, implemented fixes to restore proper spin intervals, and revised its internal testing protocols to incorporate more precise measurement tools, and these actions formed part of the settlement package presented to the commission.
The regulator noted that the provider cooperated fully throughout the process, supplied detailed records of the affected releases, and demonstrated that the issues had been resolved before any external enforcement action became necessary, and this cooperation influenced the final settlement terms.

Regulatory Context and RTS 14 Requirements
RTS 14 forms part of the broader framework that governs how remote gambling products are designed and deployed in Great Britain, and the standard aims to prevent features that could encourage rapid, repetitive play without adequate pauses, and operators along with their software suppliers must demonstrate ongoing compliance through documented testing procedures.
The commission continues to monitor adherence to these standards across the licensed sector, and cases like this one illustrate how even unintentional technical shortfalls can trigger regulatory scrutiny when games reach the market, and suppliers therefore maintain updated quality assurance processes to align with evolving expectations.
Settlement Terms and Industry Implications
The agreed payment of £122,835 represents the financial component of the settlement, and no further licence conditions or restrictions were attached beyond the corrective actions already completed by Stakelogic BV, and the commission's announcement serves as a public record of the resolution reached in this instance.
Observers note that self-reporting remains an established route for addressing compliance gaps, and when providers identify and rectify issues promptly the regulator takes those steps into account when determining outcomes, and this approach encourages transparency while still upholding the technical standards that apply to all licensed activity.
Software testing practices have evolved alongside regulatory expectations, and many suppliers now supplement manual checks with automated timing scripts that log exact spin intervals across large volumes of test spins, and such layered verification reduces the likelihood of similar deviations occurring in future releases.
Conclusion
The Stakelogic BV settlement underscores the commission's ongoing focus on product design standards that protect players through enforced pacing mechanisms, and the case highlights both the challenges of maintaining precise technical compliance across multiple game titles and the value of proactive reporting when issues arise, and the details released in June 2026 provide a clear account of how the matter was identified, addressed, and concluded without further escalation.