Gamdom Crash Live Tracker

Every round is read server-side from Gamdom’s public crash history, polled every 20 seconds and stored before it reaches this page. Nothing here is simulated or modelled, and the board covers Gamdom’s own Crash table only — no other Gamdom Original, no other casino. Each row carries the crash point, Gamdom’s published game time and the bets that round listed; our Gamdom verifier rebuilds any of them from its published game hash.

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

The newest settled round sits alone at the top of the board and the strip beside it lists recent rounds, newest first; both redraw as each round settles. Of the 2,500 rounds the feed held at 03:06 UTC on 15 September 2026 — back to 06:28 UTC on 14 September 2026 — 1,217 cleared 2× and 261 cleared 10×. These are settled rounds, not bets: no stake or payout is attached to them.

A round reaches the page within about half a minute of Gamdom publishing it: our collector polls every 20 seconds and your browser re-reads our feed every 8. The live pill turns stale once the feed on screen is more than two minutes old, which at the feed’s median 23-second gap is about 5 rounds. Times in the round log are Gamdom’s own published game times, shown in your local zone.

The page loads the 2,500 most recent rounds — 20.6 hours at Gamdom’s pace, back to 06:28 UTC on 14 September 2026 in a feed read at 03:06 UTC on 15 September 2026. The window tabs are round counts, not clock windows: Last 100, 500, 1,000 and 2,500, opening on Last 100. Export CSV writes all 2,500 loaded rounds with UTC timestamps whichever tab is showing. The head’s rounds tracked figure, 86,929 since 16 August, is our whole store.

About 121 an hour measured over the loaded buffer: 2,500 rounds spanning 20.6 hours to 03:06 UTC on 15 September 2026. The head’s rounds / hour reads higher, 157, because it is 3,600 divided by the feed’s median 23-second gap and a median ignores the long pauses. The mean gap was 30 seconds, one gap in ten ran 52 seconds or more, and the longest ran 144.

2,611.98×, at 09:44 UTC on 14 September 2026 — the highest of the 2,500 rounds the feed held at 03:06 UTC on 15 September 2026. 2 of those rounds cleared 1,000× against 2.5 expected on the 99% model. A crash point is where the round ended, not a player’s win: the 10 bets that round listed all cashed out earlier, at points this feed does not carry. The peak, 24 h figure below the strip reads that same buffer, about 20.6 hours.

The published model is 99%, not 100%: Gamdom Crash carries a 1% house edge, so P(crash ≥ T) = 0.99 ÷ T at every cash-out target. Rewards paid outside the round, such as the rakeback described in our Gamdom review, do not change that. The feed carries crash points and no stakes, so the page measures return by target rather than certifying it: over the 2,500 rounds to 03:06 UTC on 15 September 2026 it ran 97.4% at 2× and 122.0% at 50×.

50 of the 2,500 rounds to 03:06 UTC on 15 September 2026 ended at 1.00× — 2.00%, one round in 50, against the 1.98% the 99% model gives and the 0.99% the same formula returns with no house edge. Rounds finishing under 2× came to 1,283, 51.3%, where the model expects 50.5%, and the median crash point was 1.94×. Neither gap against the 99% model is larger than ordinary sampling noise at this size.

No. The droughts panel counts how many rounds passed between hits of the target you pick, and nothing here predicts anything — every round is independent. In the 2,500 rounds to 03:06 UTC on 15 September 2026 the longest run without a 10× was 50 rounds and the longest without a 50× was 241. Each crash point comes from that round’s own game hash, so the chance the next round clears 10× stays 9.9% however long the drought has run.

Paste the round’s published game hash into our Gamdom verifier, which hashes in your browser and posts nothing to a server. Gamdom’s Crash runs on a reverse SHA-256 chain: SHA-256 of one round’s hash equals the previous round’s hash, so a single hash checks every round before it. The crash point is an HMAC-SHA256 of Gamdom’s published salt keyed on that hash, with an instant 1.00× when the digest divides by 100. The snippet covers rounds after 2 January 2026.

They count the bets Gamdom’s public round history lists for a round, and how many of those carried a cash-out. Across the 2,500 rounds to 03:06 UTC on 15 September 2026 the cash-out share tracked the crash point: none of the 1,089 bets on the 1.00× busts, 14.6% between 1.5× and 2×, 81.3% past 10×. Those bets arrive in mixed display currencies, so Gamdom publishes no single-currency wagered total and no flight time, and this page shows neither column.

Different windows and different games. Our tabs are round counts, so the span each one covers moves with Gamdom’s pace — Last 2,500 held 20.6 hours in the read at 03:06 UTC on 15 September 2026 — while a tracker cutting a fixed clock window holds a different set of rounds. The log prints your local time and the CSV export UTC. The same 99% model drives our Stake Crash tracker, Shuffle Crash tracker and BC.Game Crash tracker, on separate games whose counts never match this one.

It cannot certify a game; it can measure one. Across the 2,500 rounds to 03:06 UTC on 15 September 2026 all twelve cash-out targets in the RTP table sat within 2.1 standard deviations of the published 99% line, and the closest of them, 5×, drew 495 hits against 495.0 expected. Each round can be re-derived from its published hash in the Gamdom verifier. A sample this size would not show a one-point change in the edge, and we audit no operator.