Skip to content

Aviator Provably Fair Check: 3 Rounds Recomputed

Aviator's round results can be checked, and the check works: we took three finished rounds from Spribe's official demo on 29 September 2026 and recomputed every one of them from its seeds. The part a player can verify is the step from seeds to result. What still rests on trust is the commitment that the operator's server seed was locked in ahead of time.

In short: Yes, Aviator's results follow from published seeds, and any finished round can be recomputed in roughly a minute. Whether the operator's seed was truly committed first is the piece players must take on trust. Spribe holds a UK licence that drew a regulator's warning in June 2026.

The short verdict

The seed system does what it says on the mechanical level. Each result is derived from a hash of four inputs, three of them supplied by players, and the derivation can be repeated by hand. That's a stronger guarantee than a slot offers, where the random number generator stays inside a server.

It's not unconditional, though. Spribe's own claim that the technology "guarantees 100% fairness" is the studio's sentence, and it sits in quotation marks here for a reason: the server seed comes from the operator, and the link between the hash published before a round and the seed revealed after it is the step a player can't close alone.

How the seed system works

Spribe describes the round result as generated "from four independent participants of the round: game operator and first 3 betters of the round". Each input enters at a different moment.

ParticipantWhat it contributesWhen it becomes visible
OperatorServer seedA SHA-256 hash of the next seed shows in Provably Fair Settings before the round; the seed itself after the round
First bettorClient seed 1Fairness panel, once the round ends
Second bettorClient seed 2Same panel, same moment
Third bettorClient seed 3Same panel, same moment
GameSHA-512 hash of all four, and the result derived from itAfter the round

To be among the three contributors, a player has to be one of the first three to bet in that round. Client seeds are random for each new game by default, can be entered manually, and can't be changed while a bet is active. Each game room generates its results independently, with its own server and player seeds, and the fairness window can show a "Not enough players" label.

How we recomputed three rounds

The test took a few minutes per round. We opened the fairness panel for a finished round, copied the server seed and the three client seeds, joined the four strings in that order with nothing between them, and ran SHA-512 on the result. Then we compared our hash with the one on the panel.

Round 11965562 is the worked example. The panel showed the server seed and three client seeds; our SHA-512 matched the panel's hash. The first 13 hexadecimal characters of that hash, e7d4d1b68560a, are the panel's Hex field, and they read as the decimal 4078419799725578, which the panel also printed. Putting that number into floor(97 × 2^52 / (2^52 − h)) / 100 gives 10.27, exactly where the round ended.

RoundEnded atSHA-512 matched the panelFormula reproduced the result
1196556210.27xYesYes
119655772.43xYesYes
119656091.64xYesYes

Three rounds is a check of the method, not an audit of the game. It shows that a result follows from its seeds by a fixed rule, and it lets any reader repeat the same steps on a round of their own choosing.

What rests on trust

The weak link is the commitment. The Provably Fair Settings screen publishes a SHA-256 hash labelled as the next server seed, and during our session we watched that published value rotate. The client documents neither the rotation rule nor which published hash belongs to which revealed seed, and every room runs its own seeds. So the derivation is checkable by the reader; the promise that the server seed was fixed before the round, rather than chosen afterwards, rests on trust in the operator who generates it.

Three client seeds blunt that risk without removing it. An operator can't know those inputs before players bet, which makes steering a specific result far harder than with a hidden server-only generator.

Licences, stated plainly

Spribe's licensing record is mixed, and it reads best with the dates attached.

JurisdictionWhat the record shows
United KingdomGambling Commission account 57302, licence 057302-R-333085-003 for gambling software, active since 8 December 2020; a game host activity is pending
MaltaRecognition Notice RN/189/2020, not a licence from the Maltese regulator; no entry in its licensee register
EstoniaCompany registry code 14540763, entered 8 August 2018
SwedenA warning and a sanction fee of 5,000 kronor for supplying software to operators without the necessary Swedish licence
CuraçaoNo entry for Spribe in the regulator's registry file of 21 September 2026, which lists 665 licensees

On Curaçao, one detail causes confusion. Spribe's demo launcher passes a parameter reading jurisdiction=CW. That's a session configuration value, not a licence, and any Curaçao licence number attributed to Spribe is false.

The UK warning of June 2026

The UK Gambling Commission's register records one regulatory action against the account. On 12 June 2026 the Commission found that Spribe "had been operating without the appropriate licence between 28 May 2021 and 30 October 2025" and imposed a warning under section 117(1)(a) of the Act. The Commission had suspended the licence on 30 October 2025 and lifted the suspension on 30 March 2026.

The same decision states that Spribe "co-operated with the Commission throughout the investigation and took corrective steps to address the identified concerns." Both halves belong in any honest summary: a serious compliance failure over more than four years, and a regulator that chose a warning and recorded cooperation.

What the test-lab claim covers

The game shows an in-game notice that it "is tested by certified laboratory, licensed by UKGC, MGA and other authorities." The UK register supports the first authority on that list; the Maltese registers contradict the second, since Spribe appears only in the Recognition Notice register. The notice names no laboratory, no certificate number and no date, and no test house runs a public per-title register for Aviator. Spribe lists company-level and jurisdiction-level certificates on its own site, which are a different thing from a certificate for this title.

Who should rely on what

For a player who wants to know whether a crash point was rigged after the fact, the seed panel is a real tool, and recomputing a round is worth doing once just to see it work. For a player who needs institutional assurance, the UK licence is the substantive one, read together with its June 2026 warning. We do not recommend leaning on the in-game laboratory notice for anything; it carries no checkable detail.

Seeds also explain why no predictor can work, which the predictor warning covers, and why the 97% figure appears inside the round formula, explained on the RTP page. The Aviator overview gathers the rest. The game itself is restricted to players aged 18 or older.

FAQ

Who generates the server seed?

The operator running the game generates it, according to Spribe's description, not Spribe itself. Its hashed form is published before play begins.

Can a player change their own client seed?

Yes, it is random per game by default and can also be typed in manually, but it stays locked whenever that player has a live bet.

Does Spribe hold a Maltese licence?

No, in Malta Spribe holds a Recognition Notice numbered RN/189/2020, which recognises an authorisation from another country, and it has no entry in the Maltese licensee register.

Is there a lab certificate for Aviator itself?

No laboratory publishes a per-title certificate for Aviator. The in-game notice about a certified laboratory names no lab, number or date.