Aviator isn't quite the 99% game you're used to.
Aviator is Spribe's crash game — the most widely-licensed branded version, showing up across dozens of casinos. It runs the same win-chance shape as the Crash calculator, but with a lower RTP plugged in: publicly cited at 97%, not 99%.
A lower number, not a different game.
Aviator's win chance is still RTP ÷ target — identical shape to every crash game. The difference is which RTP gets plugged in: Spribe publishes 97% for Aviator, versus the ~99% convention this site's calculator and most in-house Stake/BC.Game Crash implementations cite. Spribe also allows operators to configure Aviator as low as 94–96%, so the actual number can vary by casino.
An instant crash at 1.00× — no chance to cash out at all — happens exactly as often as the house edge, by construction of the formula. Aviator's edge is 3 percentage points bigger than this site's convention, so instant crashes are 3 times more frequent.
Every target, both RTPs.
| Target | Aviator (97%) | This site (99%) |
|---|---|---|
| 1.5× | 64.67% | 66.00% |
| 2× | 48.50% | 49.50% |
| 3× | 32.33% | 33.00% |
| 5× | 19.40% | 19.80% |
| 10× | 9.70% | 9.90% |
| 20× | 4.85% | 4.95% |
A published formula, independently audited.
Seed, client seed, and a salt
Spribe combines a server seed, your client seed, and a salt value, hashed with SHA-256/SHA-512 to produce a value the crash point is derived from.
Committed before the round
The hash is generated and fixed before the round starts — the exact crash point can't be adjusted once betting opens, only revealed and verified afterward.
Independently audited
Spribe's provably fair system has been reviewed by third-party labs (iTech Labs, GLI, BMM Testlabs), on top of the seed-based verification any player can run themselves.
The 97% figure is Spribe's own publicly cited number, not something we've independently re-derived round by round. Because Spribe licenses Aviator to many operators who can configure the RTP within Spribe's allowed range, the exact figure at any specific casino could differ slightly — check that casino's game info panel for the number that actually applies to your bets.
Questions specific to Aviator's version.
Is Aviator the same math as this site's Crash calculator?
The shape is identical — win chance is RTP ÷ target on both. The number that changes is the RTP itself: this site models the 99% crypto-casino convention, Aviator is cited at 97% (and can be configured lower by individual operators within Spribe's allowed range).
Why does Aviator "instant crash" at 1.00× more often than other crash games?
The instant-crash rate equals the house edge by construction. Aviator's edge (~3%) is roughly 3 times larger than the 1% convention used elsewhere on this site, so its 1.00× instant crashes are proportionally more common too.
How is Aviator's crash point actually calculated?
The published approach combines a server seed, client seed and salt, hashed, then converted to a crash point using the same inverse-formula shape as any other crash game.
The formula
- Win chance for target m is RTP ÷ m — the chance the crash point lands at or past m.
- RTP is Spribe's configured value for that operator, cited around 97% publicly.
- Instant crash happens whenever the hash-derived value would put the crash point below 1.00×, clamped to exactly 1.00× instead.
Worked example — 2× target
- Aviator (97%) win chance: 0.97 ÷ 2 = 48.50%
- This site (99%) win chance: 0.99 ÷ 2 = 49.50%
- Gap: 1.00 percentage points, purely from the RTP difference
Is there a pattern to when Aviator crashes early?
No — each round's crash point is drawn independently from the same distribution every time. A run of early crashes carries no information about the next round; the hash-based generation has no memory of past rounds.
Can a "predictor" tool see Aviator's crash point in advance?
No. The crash point is committed via a cryptographic hash before the round starts and only revealed afterward for verification — nothing running in a browser during the round has access to a number that hasn't been generated yet.
Is there a best target to use on Aviator?
No — every target carries the same underlying edge, whatever Aviator's configured RTP is at that operator. The full breakdown of what a target does and doesn't change is on the Crash strategy page.
Why do some Aviator reviews cite a different RTP than 97%?
Spribe permits operators to configure Aviator at a lower RTP (down to roughly 94%), so different casinos running Aviator can legitimately cite different figures. 97% is Spribe's own headline number, not a guarantee for every operator.