BC.Game Crash Live Tracker

They come from BC.Game’s own Crash original — its public round history, polled server-side every ten seconds. Nothing here is simulated. Those rows carry a round id, the crash point and each round’s begin and end times, but no stake, cash-out or bettor fields, so the board shows none. We had stored 96,537 rounds by 03:27 UTC on 15 September 2026. Expected throughout means P(crash ≥ T) = 0.99 ÷ T, from a 1% house edge. Your own bets rebuild in our BC.Game verifier.

Feed data is published under CC BY 4.0: reuse it freely, credit casinodrop.com and link the licence.

The newest settled round sits at the top of the board and the strip beneath it runs newest first. Across the 2,500 rounds the feed held at 03:27 UTC on 15 September 2026 — back to 07:22 UTC on 14 September — the median crash point was 2.02× against a theoretical 1.98×, 48.9% of rounds ended under 2× and 44 busted at 1.00×. The window tabs recut every panel over the last 100, 500, 1,000 or 2,500 rounds.

2× was reached in 51.1% of the 2,500 rounds the feed held at 03:27 UTC on 15 September 2026 — 1,277 rounds — against the 49.5% a 1% house edge implies; 10× in 9.2%, 230 rounds, against 9.9%; 100× 27 times, 1.08%, against 0.99%. 44 rounds busted at 1.00×, 1.76%, against 1.98%. All four describe one sample of about 20 hours, not the game’s lifetime.

BC.Game Crash returns 99% at every cash-out target under the 1% house edge this board and our verifier use; BC.Game publishes no RTP figure of its own. Because P(crash ≥ T) = 0.99 ÷ T, expected return at 1.5× and 50× is identical; only the variance differs. The RTP table estimates it from results, hits × target ÷ rounds, never from money: the feed carries no stakes. Over the 2,500 rounds held at 03:27 UTC on 15 September 2026 it came to 102.2% at 2× and 92.0% at 10×.

The Peak in window tile and the peak, 24 h figure under the strip both name the highest crash point among the rounds the page currently holds, so it is a rolling figure rather than an all-time record. At 03:27 UTC on 15 September 2026 that was 4,949.05×, in a round lasting 141.7 seconds and already 948 rounds from dropping out of the buffer. It is a crash point, not a payout: BC.Game publishes no stakes, cash-outs or winners here.

About 125: 2,500 rounds settled in the 20.1 hours to 03:27 UTC on 15 September 2026, and the whole 96,537-round store averages 122.7 an hour since 13 August. The head’s rounds-per-hour fact read 156.5 at that moment because it is 3,600 ÷ the 23-second median gap, which discounts the long rounds. Half the rounds ran under 11.7 seconds, and the median pause between one crash and the next start was 12.1 seconds.

Because a round ends when the multiplier crashes, and the times BC.Game publishes grow with it at a fixed rate. Across the 2,456 rounds above 1.00× in the feed at 03:27 UTC on 15 September 2026, round length matched ln(multiplier) ÷ 0.0601 to within a median 0.03 seconds — about 6.2% a second, doubling every 11.5 seconds. So 2× takes 11.5 seconds, 10× takes 38 and 100× takes 77. That describes the times BC.Game published, not a rule it states.

This page holds the newest 2,500 rounds, about 20 hours of play; the store behind it held 96,537 rounds at 03:27 UTC on 15 September 2026, back to 08:49 UTC on 13 August. BC.Game’s own history call returns only the last 100 rounds and rejects a larger page size, so anything deeper exists only where somebody kept polling. Export CSV writes all 2,500 held rounds — UTC timestamp, multiplier, round seconds — ignoring the window and the log filter.

They count the rounds between hits of the target you pick and set that against the wait a 1% house edge implies; they predict nothing. The longest run without a 10× among the 2,500 rounds held at 03:27 UTC on 15 September 2026 was 78 rounds, and a gap that long turns up in 7% of 2,500-round stretches. Every round is drawn on its own, so after a drought of any length the chance of reaching 10× is still 9.9%.

Only for a bet you placed yourself: reveal your seed pair in your BC.Game account, then rebuild that bet in our BC.Game verifier, or replay a run of nonces in the seed simulator. Both sign HMAC-SHA256(serverSeed, "clientSeed:nonce") with no Stake-style cursor, read the first 13 hex characters as a 52-bit draw and apply the 1% edge. The rounds listed on this board are not verified one by one.

Because BC.Game’s public round history does not publish them — each row carries the round id, the crash point, the begin and end times and a hash and salt, and nothing about bets. The board draws only the fields the feed actually carries, so those tiles and columns are absent rather than filled with zeros, and Round length takes the activity panel’s place. BC.Game’s own game page describes Classic and Trenball betting modes; no bets reach us, so neither is broken out.

A round reaches the page within about 18 seconds of BC.Game publishing it: the collector polls every 10 seconds and rewrites the feed each time, and your browser re-reads that feed every 8. The head shows how long ago the feed was written, and its pill turns from live to stale once that passes two minutes, with a banner saying the numbers are real but not current. When a poll fails the rounds already received stay on screen; nothing is invented to cover the gap.

Mainly because every tracker holds a different set of rounds. BC.Game’s history call reaches back only 100 rounds, about 48 minutes at this pace, so each site’s depth is whatever it has collected since it started — ours began on 13 August 2026 and held 96,537 rounds by 15 September. Our windows count rounds rather than hours, and our timestamps are UTC while the log shows local time. The other CasinoDrop trackers sit on one hub.