Pick a stake and a cash-out, then see what that bet returned over every round we've recorded, and how it plays as sessions with a bankroll: typical runs, bad ones and how often the money ran out. History, not a prediction.
Every recorded round
Rounds203,789
Won49.6%the game's maths: 49.5%
Staked€203,789
Returned€202,044
Net-€1,745
Return99.14%
€1 a round at 2.00x, 203,789 rounds.
Sessions
Bankroll
€
Session length up to 203,789
rounds
Sessions from
Typical end balance€98
Middle half€88 to €108
9 in 10 sessions€72 to €126
Ended ahead42.9%
Went broke0.0%
Longest losing run–
Deepest drawdown–from a running high
9 in 10 sessions middle half typical session starting bankroll
2,000 × 250 rounds (random draws from 203,789) · €100 start · €1/round · 99.27% returned
Luck check
Check your own session.
Rounds played
rounds
Your result
€
100 rounds, €1 a round, cashed out at 2.00x: expected -€0.86, 9 in 10 end -€18 to +€16. Enter your result.
GambafishLuck check
UnluckyAverageLucky
Expected
9 in 10 sessions
49.57% of 203,789 rounds reached 2.00x.
Round history
Time
Multiplier
12:33
1.46x
12:32
1.32x
12:32
1.42x
12:32
3.28x
12:31
1.92x
12:31
2.95x
12:30
1.03x
12:30
1.49x
12:30
2.45x
12:30
1.09x
12:29
1.07x
12:29
1.04x
12:29
2.16x
12:29
3.20x
12:28
5.10x
12:28
1.28x
12:27
2.83x
12:27
7.24x
12:26
3.33x
12:26
1.79x
12:25
12.31x
12:24
6.16x
12:24
5.92x
12:23
1.40x
12:23
4.82x
12:22
1.02x
12:22
10.01x
12:21
2.43x
12:21
1.02x
12:21
1.13x
All rounds
Time
Multiplier
Page 1
The longest run of rounds under 2x in more than 125,000 BC.Game Crash rounds has reached 14, and a script doubling its bet at 2x would have needed 32,767 times its first stake to sit through it. This BC.Game Crash tracker keeps that history: every round of the current salt, rebuilt from the hash BC.Game reveals for it, newest first, with about 3,000 more added each day.
BC.Game Crash results today and the last 7 days
Day (UTC)
Rounds
Under 2x
Highest multiplier
Today so far, Sun 22 Nov
1,723
49.2%
3,095.57x
Sat 21 Nov
3,287
52.1%
2,107.84x
Fri 20 Nov
3,231
49.3%
12,392.19x
Thu 19 Nov
3,289
51.0%
17,902.35x
Wed 18 Nov
3,330
51.0%
1,320.3x
Tue 17 Nov
3,284
50.9%
5,936.07x
Mon 16 Nov
3,070
48.6%
3,949.06x
Sun 15 Nov
3,119
50.3%
2,104.47x
Key takeaways
The longest run under 2x in our record has reached 14 rounds; doubling from one unit through it loses 16,383 units and asks 16,384 more for the next bet.
About 1.95% of rounds stopped at 1.00x, the share BC.Game’s round-down formula sets, so a 2.00x on screen means the round truly reached 2x.
Orange rounds under 2x took about 50.5% and green rounds about 49.5%, with 10x or more on about 9.9%.
For every 100 staked at a 2x auto cash-out, about 98.96 came back, about 98.94 at 1.5x and about 99.1 at 10x.
The top round passed 158,000x, while 1,000x or more came about once in 1,150 rounds, a little rarer than the formula’s once in 1,010.
Why a BC.Game crash script needs a longer history
A script running inside the game sees only the last couple of dozen rounds, which is far too few to judge a betting plan. This page holds the whole run of the current salt instead. The Strategy backtester replays one stake at one auto cash-out over every recorded round, and its session view plays the same plan through recent rounds in the order they happened, bankroll included. That is the honest test for a script idea before any money rides on it, and it needs no code or download.
How long BC.Game Crash can stay under a payout
Rounds under 2x in a row
A doubling script has lost
Its next bet
5
31 units
32 units
10
1,023 units
1,024 units
14
16,383 units
16,384 units
The longest stretch under 2x in our record has reached 14 rounds; the higher targets wait far longer. The game has gone more than 75 rounds without a 10x, roughly 35 minutes, more than 750 without a 100x, roughly six hours, and more than 6,000 without a 1,000x, about two days at the normal pace. A doubling plan aimed at those higher targets would never get that far: its stakes outrun any bankroll, or the table’s maximum bet, within a few dozen losses.
Trenball’s red, green and moon bands in the record
Trenball bets on the same rounds as the main game, only by band: under 2x, 2x or more, and 10x or more. Over our rounds the low band took about 50.5%, 2x or more about 49.5%, and 10x or more about 9.9%, each on the share the 1% formula gives. Our chips follow the colours of the game’s own history bar, orange under 2x and green from 2x, while Trenball calls the low band red; the payouts for each band are shown in BC.Game’s bet panel, and our BC.Game Crash review explains the side game.
Checking a BC.Game round from its hash and the salt
After each round BC.Game reveals its hash. Run through a keyed hash function with a fixed public salt, it yields a number that the formula turns into the crash point, rounded down to two decimals, which is why about 1.95% of rounds show 1.00x rather than the 1.5% that ordinary rounding would leave. Each hash also leads back to the one before, so a single revealed hash lets anyone rebuild the recent past. Our BC.Game Crash fairness check follows the rebuilt rounds against the formula’s odds.
Predictor bots, APKs and prediction-today posts
None of them can see the next crash point, because it sits behind a hash that hasn’t been revealed. The record backs that up: after one to six rounds under 2x in a row, the next round reached 2x between about 49.4% and 50% of the time, against 49.5% over every round, and no hour of the day stands out either. What these offers usually want instead is a login, an APK installed from outside an app store, or a fee for a private group.
A script that bets every BC.Game round places about 125 bets an hour, and at a 1% edge it gives up around 1.25 base stakes an hour on average, more in a bad hour; if that stops being entertainment, our responsible gambling page lists where to get support.
Announcements
ResolvedFrom to
BC.Game Crash was down for a system upgrade for about two hours
No BC.Game Crash rounds were played from 01:00 UTC on 10 November until about 03:00 UTC, roughly two hours. BC.Game took its whole site offline for a system upgrade and showed its own maintenance notice on every page. The site came back at about 02:20 UTC, and Crash resumed about 40 minutes later with game 9,778,987, the next round in the same chain.
BC.Game announced the maintenance on X for 01:00 to 02:30 UTC and asked players to finish any active bets beforehand. The post went out at 01:47 UTC, after the maintenance had already started, and BC.Game has since deleted it.
BC.Game Crash is running again, and new rounds appear above as they settle.
Frequently asked questions
Does BC.Game keep a full crash history?
The game itself shows only recent rounds, and a script reading them in game gets a short list. Because every revealed hash leads back to the one before it, earlier rounds can be rebuilt exactly, and this page keeps every round of the current salt in one place, with a See all view that pages back through all of them.
What is the longest losing streak in BC.Game Crash?
In our record the longest run under 2x has reached 14 rounds, the longest without a 10x has passed 75, and the longest without a 100x has passed 750, about six hours of play. Longer runs are always possible: each round is independent, so a record streak is a record, not a ceiling.
Can the trend chart predict the next BC.Game crash?
No. The chart shows rounds that are already settled, and the next crash point comes from a hash nobody has seen yet. In our record, after one to six rounds under 2x in a row the next round still reached 2x roughly half the time, the same as any round.
Turn on notificationsPick your games, crash points and CS2 teams. No account needed.
We'd like to use Google Analytics to see which pages are read and how people find us. It sets
cookies and sends usage data to Google, so it only runs if you agree.
Privacy policy