The interface is compact, but each state matters. A bet must be accepted before take-off and Cash Out must settle before the server closes the round.
Countdown, flight and result states
The countdown accepts bets. The flight state displays the rising multiplier. The result state records the crash multiplier and prepares the next round.
A late tap can belong to the next round or fail. Always read the button text and accepted-bet indicator rather than guessing from animation.
The two betting panels
Each panel has its own stake, Bet button and Cash Out action. They can use different amounts or Auto Cash Out values.
Two panels are not a hedge against an early crash. If both are active when the round ends, both stakes lose.
- Panel one and panel two settle separately
- Each requires an accepted bet
- Each can use its own automatic settings
- Total exposure is the sum of both stakes
History, live bets and chat
Round history helps locate a completed result; it does not predict the next one. Live bets show other users’ activity but cannot alter the crash point.
Treat chat links, phone numbers, Telegram handles and predictor offers as untrusted. No player in the chat has access to the next result.
Provably Fair and settings
The fairness control exposes data for checking completed rounds. The sound, animation or data-saver settings change presentation, not mathematics.
When a dispute occurs, record the round identifier, time, bet amount and settled status before contacting operator support.
Frequently asked questions
When can I place a bet?
Only during the countdown, before the round starts.
What does Cash Out do?
It requests settlement at the active multiplier. It must complete before the round ends.
Why are there two Bet buttons?
Aviator supports two independent stakes in one round.
Does round history show a pattern?
It shows completed results only. It cannot forecast the next independent crash point.
Can chat users send reliable signals?
No. Chat users cannot see future results, and external signal links can be scams.