Stakelogic to pay £122,835 for slots that ran under RTS 14's 2.5 seconds
The Gambling Commission's June settlement with the supplier turns a technical standard into a measurable failing: sixteen games, margins as fine as a thousandth of a second, and compliance checked on a manual stopwatch.
Most of the rules that shape a GB slot read like taxonomy: categories, prohibitions, things a game may not be. RTS 14 is a number, and a number can be measured. On 25 June 2026 the Gambling Commission published the outcome of an investigation in which Stakelogic BV agreed a regulatory settlement of £122,835 after games from the supplier ran their game cycle faster than that number allows.
What the rule actually says
The requirement is short. Per the Commission’s remote gambling and software technical standards, a minimum of 2.5 seconds must elapse from the time a slot game is started until the next game cycle can be commenced; casino games other than slots and peer-to-peer poker are given 5 seconds. That is the whole organ: it governs how quickly the machine will let you go round again, and nothing else.
Sixteen specimens, measured
Per the Commission’s published account, sixteen games were affected — Tiger Temple 88, the one title named, and fifteen more found non-compliant on re-testing. The compliance periods are as published: 28 to 30 May 2025 for Tiger Temple 88, and periods between 31 October 2021 and 30 October 2025 for the other fifteen. The margins are the striking part: between 0.001 and 0.675 seconds below the minimum. At the fine end that is a thousandth of a second. At the coarse end it is two-thirds of a second clipped from every cycle — across an evening, a measurably faster machine than the standard describes.
The Commission also recorded how the timing was checked, and that detail will outlive the figure: it says it is unacceptable that the business relied on a manual stopwatch to measure the speed of its games. For a requirement policed to three decimal places, a thumb on a stopwatch is not an instrument.
The reading
Two things belong on the label. First, this is a technical-standards failing about game-cycle timing, not a fairness, payout or RNG failing. Nothing in the published outcome suggests anyone was defrauded or short-changed, and filing it under “slots caught cheating players” would misread the notice.
Second, note who the Commission acted with: Stakelogic BV, which supplied the games, not the casinos that ran them. The standards bind gambling software licensees and remote gambling licensees alike, and the published account does not apportion the duty between studio and site; it records only that the cycle these games shipped with was short. GB players meet slots already trimmed for this market — a trimming whose consequences for the shelf we catalogued earlier this month. This outcome shows the trimming is checked title by title.
One practical corollary. Cycle speed is the rate at which a balance is consumed: fewer spins an hour is simply a slower spend. Put a clock on the session rather than a spin count on it, and leave the 2.5 seconds to the regulator.