Stakelogic BV Reaches Settlement Over Slot Spin Timing Shortfalls

The UK Gambling Commission has confirmed that software provider Stakelogic BV will pay £122,835 under a regulatory settlement after several slot titles failed to maintain the required minimum gap between spins, and the breach extended across multiple years from 2021 through 2025.

Investigators found that certain games allowed spins to occur faster than the mandated 2.5-second interval, with recorded shortfalls ranging from 0.001 to 0.675 seconds below the limit, and one title affected was Tiger Temple 88; the shortfall arose because manual stopwatch checks produced inaccurate results rather than any deliberate design choice.

Details of the Identified Breaches

Commission staff examined game logs and discovered repeated instances where the interval between spins dropped below the threshold set out in the Remote Technical Standards (RTS 14 – Responsible Product Design), which requires operators to enforce a minimum 2.5-second pause so players have time to consider each outcome before the next spin begins.

The affected titles ran on platforms supplied by Stakelogic BV, and testing revealed the timing errors persisted across different casino sites that hosted the games, yet the company had relied on stopwatch measurements that proved insufficient to detect the small but consistent shortfalls.

Company Response and Corrective Steps

Stakelogic BV self-reported the issue once internal reviews highlighted the discrepancy, and the firm immediately suspended the implicated games while it recalibrated timing controls; updated testing protocols now incorporate automated measurement tools that replace manual stopwatch checks with precise digital timestamps.

Commission records show the settlement amount reflects both the duration of the non-compliance and the provider’s cooperation throughout the investigation, including full disclosure of affected game versions and prompt implementation of revised quality-assurance procedures.

Regulatory Context and Standards Application

Under Remote Technical Standards (RTS 14 – Responsible Product Design) the 2.5-second rule forms part of broader responsible product design requirements aimed at reducing the pace of play and giving players clearer decision points between spins, and the standard applies to all remote slot products offered to UK customers.

Commission guidance states that providers must demonstrate through verifiable data that their games meet the timing threshold on every deployment, and reliance on manual methods alone does not satisfy the expectation for consistent compliance across software releases.

Industry Implications for Testing Procedures

Observers note that other software suppliers have since reviewed their own quality-control processes in light of this case, and several have introduced automated scripts that log spin intervals at millisecond resolution to avoid similar discrepancies, while the Gambling Commission continues to monitor submissions for evidence that manual testing has been supplemented or replaced by digital verification.

The settlement does not include licence suspension or additional financial penalties beyond the agreed sum, because the provider acted quickly to remove non-compliant titles and supplied detailed remediation evidence that satisfied the regulator’s requirements for corrective action.

Timeline of Events

Issues first appeared in game builds released during 2021, continued undetected through subsequent updates, and remained present until early 2025 when the provider’s internal audit flagged the timing shortfalls; once identified, the games were withdrawn from UK-facing sites within days, and revised versions passed re-testing before being restored.

Throughout the investigation the Commission worked with Stakelogic BV to verify that no player funds were at risk and that the timing errors did not interact with other responsible gambling features such as session limits or reality checks.

Conclusion

The settlement closes the regulatory matter for Stakelogic BV while reinforcing the expectation that all software providers maintain rigorous, automated checks against every element of the Remote Technical Standards, and the case illustrates how self-reporting combined with swift corrective measures can result in a proportionate outcome rather than prolonged enforcement proceedings.