Live / Slots
Crash Burst sits in our slots and crash-game category — a fast-format title where you set your stake, watch a rising multiplier, and decide when to collect before the burst ends the round.
Crash Burst belongs to the crash-game genre — a category where outcome speed and player-controlled collect timing define the session rather than reel spins or card draws. Inside the xc660 lobby, it sits in the crash and fast-format game rail, making it straightforward to locate when you browse by category.
Crash Burst keeps its round structure visible at all times — stake field, multiplier display and collect button are the three things you interact with. Before each round opens, you enter your stake.
Set your stake amount in the input field before the round begins. The field shows the minimum and maximum stake range configured for your account tier. Adjust it each round or keep it fixed — the choice is yours before the timer closes.
Once the round starts, a multiplier rises from its base value. There is no fixed ceiling published in the interface — it can burst at any point. The current value is shown prominently in the centre of the game screen throughout the round.
Tap or click the collect button at any point while the round is live. Your return is your stake multiplied by the value shown at the exact moment you collect. Waiting longer increases the potential return but also increases burst risk.
A scrollable strip below the game frame shows the multiplier values from recent completed rounds. This is informational — each round runs independently, so past values do not alter the probability of any future outcome.
Crash Burst surfaces its key controls directly on the game screen — stake input, live multiplier, collect button and round history are all visible without navigating away.
RTP is shown only where the game provider publishes it within the game frame or its linked rules document. xc660 does not state a separate figure — check the in-information panel for the value the provider has disclosed.
Crash Burst is a crash-format game. Outcomes are determined round by round with no carry-over state. It is categorised under crash and fast-format games in the lobby, distinct from slot reels and live dealer tables.
Open xc660 in your mobile browser, log in, and navigate to the crash or fast-format category rail. Crash Burst loads directly in the browser window — no app download required. It also runs on desktop browsers without any plugin.
The rules and payout structure approved by the game's publisher are accessible from the information or menu icon inside the game frame. That document is the correct reference for mechanics, stake limits and any additional terms.
If something in a Crash Burst round does not resolve as expected — a collect action that did not register, a stake deducted without a round completing, or a screen that froze mid-round — our support routes are the right place to raise it.
Every completed Crash Burst round is recorded in your account transaction and game history. Open the history section from your account menu, locate the round by date and time, and copy the round reference before contacting support. This cuts resolution time significantly.
Live chat is accessible from the support icon in your signed-in account area. Use it to report a round dispute, a stuck screen or a stake query. Have your round ID and account details ready. Published operating hours are shown next to the chat widget in your account.
If a Crash Burst stake was deducted but the round did not complete, check your bKash, Nagad or Rocket transaction record alongside your xc660 account history. Both references together give support the full picture needed to investigate and resolve the discrepancy.
Crash Burst is presented as a category-placed game inside the xc660 lobby, which means it is discoverable through the crash and fast-format game rail rather than requiring a direct search every session.
Crash Burst appears in the crash and fast-format category rail in the xc660 lobby. Browsing by category is the most direct route to it — faster than scrolling the full game list. The rail updates when new titles in the same format are added.
The published rules for Crash Burst are accessible from the information icon inside the game frame. This is the operator-approved document covering mechanics, stake limits and round behaviour. We reference this panel rather than restating its contents separately.
Each Crash Burst round generates a record in your account game history — stake, multiplier at collect or bust, and outcome. This trail is accessible from your account menu and is the reference point for any support query about a specific round.
xc660 does not publish a separate RTP, volatility rating or payout speed for Crash Burst. Those figures appear only if the game's publisher surfaces them inside the game frame. We keep this page accurate rather than filling gaps with invented numbers.
Quick definitions for the terms you will see on the Crash Burst game screen and in round history — written for how real players use them.
The multiplier is the number that rises during a live round. When you collect, your stake is multiplied by whatever value is displayed at that exact moment. A higher multiplier means a larger return, but the burst can end the round at any point.
A bust occurs when the round ends before you collect. The multiplier stops, the round resets and your stake for that round is not returned. Each round busts independently — prior round history does not affect when the next bust happens.
Collecting means pressing the collect button while a round is live to lock in your return at the current multiplier. Once the burst happens, collecting is no longer possible. Timing the collect is the central player decision in every Crash Burst round.
Round history is the scrollable strip showing multiplier outcomes from recently completed rounds. It is informational context — each round is independent, so the history does not change the probability or timing of any future burst.
Stake range is the minimum and maximum bet amount you can place per round, as configured for your account tier. The game screen displays the current range in the stake input field before each round starts.
A round ID is a unique reference number assigned to each completed Crash Burst round and stored in your account game history. It identifies that specific round when you contact support about a disputed outcome or missing return.
These are the questions that come up most often about Crash Burst on xc660 — answered from what we can verify about the game and how it sits in the lobby.
Log in on your mobile browser or desktop, then browse to the crash or fast-format category rail in the game lobby. Crash Burst is listed there by game type.
No download is needed. Crash Burst loads inside your mobile browser when you open xc660 and navigate to the game. The layout adapts to your screen size automatically. Desktop browsers also run it without any plugin or additional software installation required.
Yes — bKash, Nagad and Rocket are configured payment options in your xc660 account wallet. Fund your account wallet first through the deposit section, then the balance is available across all games in the lobby including Crash Burst. Check the deposit section for the current steps shown there.
Some crash-format games offer an automatic collect threshold you can set before the round starts. Whether Crash Burst includes this feature is shown on the game screen itself — look for the auto-collect or target multiplier field in the betting panel before the round opens.
If your connection drops while a round is live, the round completes on the server side according to its published rules. Rejoin as quickly as possible and check your account game history for the recorded outcome. Contact support with the round ID if the result is not reflected correctly in your account.
Open the game frame and tap the information or menu icon — this loads the published rules document provided by the game's publisher. That document covers mechanics, stake limits, collect behaviour and any additional terms. It is the authoritative source; we defer to it rather than restating it here.