What a casino’s live wins ticker really shows: losing bets too, on all 13 feeds with money
Feed research · 7-day windows ending Sep 23, 2026All 13 live wins tickers we can measure show losing bets, not just wins. We recorded the tickers of 19 crypto casinos for a week and rebuilt every figure from the rows they displayed.

Live wins ticker speed: Gamdom’s shows 16.5 rows a second, Shock’s 12 rows a minute, 82× apart
Each lane is one casino’s ticker, fastest first. Every lane scrolls at the same speed and each mark is one displayed row, so the gaps show the average wait between rows. Pace is the week’s rows ÷ the seconds our collector was running, with its two pauses taken out.
- Gamdom16.5 rows a second
- Cloudbet4.0 rows a second
- Thrill2.0 rows a second
- AceBet1.8 rows a second
- Winna1.7 rows a second
- Chips1.5 rows a second
- DegenCity1.2 rows a second
- Gamba1.2 rows a second
- Roobet59 rows a minute
- BC.Game58 rows a minute
- GOATED57 rows a minute
- Shuffle56 rows a minute
- 500 Casino54 rows a minute
- BetFury49 rows a minute
- Qzino48 rows a minute
- Whale.io46 rows a minute
- CoinCasino29 rows a minute
- Rakebit17 rows a minute
- Shock12 rows a minute
Each lane shows the week’s average pace. Real tickers move in bursts, and the silence chart below marks each one’s longest quiet stretch.
A fast ticker can be a few busy players. One account can place hundreds of bets, and the casino picks which bets its ticker shows.
Live wins ticker losses: 19.2% of displayed rows paid nothing at 500 Casino, 74.4% at Cloudbet
Yes. All 13 tickers we can measure show losing bets. Each bar splits a feed’s displayed rows at the center line. Bets that paid nothing go left, and bets that paid something go right. The six feeds we can’t split are listed under the chart, in their snapshots’ words.
Display-weighted means the whole feed returned 120% or more of the stake it captured. No run of play sustains that margin, so we read the ticker as a display the casino curates.
Rakebit and Whale.io publish only or almost only payouts, so their bars would have almost no left arm. They aren’t drawn.
A long right arm reflects which rows the casino puts on its ticker. The two display-weighted feeds returned more than the stake they captured.
Not drawn: six feeds whose money can’t be split
AceBet · Opaque units
“CCY and REAL are the feed’s own units, with no established USD, fiat or crypto value.”
CoinCasino · Snapshot discloses a possible selection
“The CoinCasino snapshot says its captured rows may be a selection (“selection, masked-label concentration and large payout tails prevent casino-wide or person-level claims”), so its money never enters a per-game or per-bucket ratio.”
DegenCity · Stakes and payouts not fully linked
“Most captured settlements have no visible parent bet, so the feed has no complete USD stake total.”
Rakebit · Publishes payouts only
“The feed shows almost only bets that paid out, so stake and payout figures would lean toward wins.”
Whale.io · Publishes payouts only
“The feed never shows a bet that returned nothing, so stake and payout figures would lean toward wins.”
Winna · Snapshot discloses a possible selection
“The Winna snapshot says its captured rows may be a selection (“may be selected or otherwise incomplete”), so its money never enters a per-game or per-bucket ratio.”
Live wins ticker silence: no new row in 40.6% of Roobet’s minutes and 17.3% of Shock’s, and the longest silence lasts 170 minutes
Each row is one ticker across the week, in UTC. The mark is its longest run of minutes with no displayed row, at the real time. The figure at the end is its share of silent minutes. Hatched bands are our collector’s own pauses, when no feed was recorded, and they never count as silence.
- Roobet40.6%
- Shock17.3%
- Winna6.0%
- Thrill4.6%
- Gamdom4.5%
- DegenCity3.4%
- Whale.io3.0%
- Chips2.9%
- Shuffle2.7%
- Rakebit2.5%
- Cloudbet2.3%
- CoinCasino2.0%
- Qzino2.0%
- AceBet1.3%
- BetFury1.2%
- BC.Game1.1%
- 500 Casino1.0%
- Gamba0.5%
- GOATED0.5%
A high silent share with a short longest gap means a ticker that refreshes in batches. Shock’s longest gap is 36 minutes, yet 17.3% of its minutes carry no row.
No feed’s longest silence begins as the collector resumes, so every mark is the ticker’s own.
Live wins ticker disclosures: 19 tickers in their own words, and no snapshot claims its feed is complete
Each card shows the feed we capture, what it publishes, the limit its snapshot discloses and the snapshot’s own sentence, quoted as written.
- 2Payouts only
- 2May be a selection
- 1Links incomplete
- 14Completeness unknown
- 500 CasinoCompleteness unknown
All Bets feed
Shows · Casino, originals and sportsbook bets
“The money figures compare observed USD stake with gross return in the public All Bets feed. They are not audited casino-wide revenue, and they do not show sportsbook settlement status.”
Its snapshot says · source.moneyContract 535,615 bets in its week
See the bet data · 500 Casino → - AceBetCompleteness unknown
All Bets · CCY and REAL units
Shows · Bets in CCY and REAL units
“unknown”
Its snapshot says · source.feedCompleteness 1,079,232 bets in its week
See the bet data · AceBet → - BC.GameCompleteness unknown
Latest Bet feed · USD totals
Shows · Stakes, payouts and games from Latest Bet
“Covers only the captured public Latest Bet rows. Source completeness and casino-wide throughput are unknown.”
Its snapshot says · feeds.latestBet.definition.financialInterpretation 581,645 bets in its week
See the bet data · BC.Game → - BetFuryCompleteness unknown
Public bet feed · USD-priced bets
Shows · Originals bets and seed fields
“unknown”
Its snapshot says · source.feedCompleteness 494,406 bets in its week
See the bet data · BetFury → - ChipsCompleteness unknown
Public Betting Feed · settled bets
Shows · Payouts, declared RTPs and Originals proof fields
“casino-wide revenue, traffic or long-run game fairness”
Its snapshot says · reviewBoundary.notAssessed 916,202 bets in its week
See the bet data · Chips → - CloudbetCompleteness unknown
Public bet feed · every currency
Shows · Bets in several currencies, converted to USD
“unknown”
Its snapshot says · source.feedCompleteness 2,405,866 bets in its week
See the bet data · Cloudbet → - CoinCasinoMay be a selection
Public feed · settled bets in USD
Shows · Currencies and settled bets
“The capture is a bounded public feed observation, not a complete casino ledger or proof of continuous collection.”
Its snapshot says · source.caveats 291,521 bets in its week
See the bet data · CoinCasino → - DegenCityLinks incomplete
Settlement feed
Shows · Payouts, many with no visible bet
“unknown”
Its snapshot says · source.feedCompleteness 719,520 settlement rows in its week
See the bet data · DegenCity → - GambaCompleteness unknown
Settled casino bets
Shows · Originals, casino bets and open sports bets
“Captured public feed, not a complete casino ledger or all Gamba activity.”
Its snapshot says · contracts.source 707,442 bets in its week
See the bet data · Gamba → - GamdomCompleteness unknown
Live Bets · settled bets
Shows · Live Bets feed, high rollers and the biggest wins
“Captured public feed, not a complete casino ledger”
Its snapshot says · source.disclosure 9,894,905 bets in its week
See the bet data · Gamdom → - GOATEDCompleteness unknown
Latest Bets · USD-priced bets only
Shows · USD bets, with $GOATED bets kept apart
“Public GOATED Latest Bets capture only. It is not the complete casino ledger.”
Its snapshot says · contracts.source 573,156 bets in its week
See the bet data · GOATED → - QzinoCompleteness unknown
Originals feed · USD stake and payout
Shows · Originals, big wins and repeated feed entries
“Covers only captured Qzino public-bet events. It is not a complete casino ledger.”
Its snapshot says · methodology.source 478,580 bets in its week
See the bet data · Qzino → - RakebitPayouts only
Public feed · positive results
Shows · Public results and game catalog
“172,607 of 172,609 captured events have a positive raw winAmount, and 2 have a zero raw return. The exception does not turn this strongly return-selected feed into an all-bets ledger. It still cannot measure casino-wide return, loss rate, turnover, revenue or house edge.”
Its snapshot says · selectionGate.conclusion 172,609 published payouts in its week
See the bet data · Rakebit → - RoobetCompleteness unknown
Public feed · USD-priced bets
Shows · Settled bets and the feed’s 100-row ceiling
“unknown”
Its snapshot says · source.feedCompleteness 586,444 bets in its week
See the bet data · Roobet → - ShockCompleteness unknown
All Bets feed · settled bets
Shows · Settled bets and original games
No completeness statement recorded.
120,120 bets in its week
See the bet data · Shock → - ShuffleCompleteness unknown
Public feed · USD-priced bets
Shows · Originals, game catalog and USD-priced bets
“This is a captured public-feed sample, not an audited ledger or theoretical game RTP report.”
Its snapshot says · reviewBoundary.cautions 557,743 bets in its week
See the bet data · Shuffle → - ThrillCompleteness unknown
Public feed · USD-priced bets
Shows · Settled bets and the weight of big bets
“unknown”
Its snapshot says · source.feedCompleteness 1,206,860 bets in its week
See the bet data · Thrill → - Whale.ioPayouts only
Public feed · positive payouts only
Shows · Published payouts and game catalog
“Covers published payout-bearing events only. Terminal losses are omitted, so ledger-wide casino metrics are invalid.”
Its snapshot says · selection.interpretation 461,852 published payouts in its week
See the bet data · Whale.io → - WinnaMay be a selection
Public feed · bets by wallet coin
Shows · Bets by VIP level and wallet
“Latest Bet RTP is the gross return divided by wager inside the observed public feed. It is not Winna theoretical RTP, audited casino RTP, or proof of complete wagering activity. The unusually win-heavy surface may be selected or otherwise incomplete.”
Its snapshot says · source.disclosure 1,048,661 bets in its week
See the bet data · Winna →
Live wins ticker vs lobby counter: BC.Game’s “playing” number is a display value, 4 of 12 samples taken
BC.Game’s lobby prints a “playing” number on every game tile, and we read it exactly as its API serves it. BC.Game doesn’t say what it counts and we haven’t verified it, so we never treat it as a head count.
Below its floor, so the lobby snapshot publishes no ranking and neither do we.
Not verified by us. It is BC.Game’s display number, read as served.
No bet-feed snapshot in scope publishes a head count.
“onlineUsers is the number BC.Game’s own lobby prints on each game tile, read exactly as its lobby API serves it. 0xCasinos has not verified it, and BC.Game does not document how it is computed. It is not a count of players 0xCasinos observed.”
Live wins ticker data: every table and note behind the charts
Every table behind the charts: ticker tabs, the feed table, cadence, payout bands, top games, currency labels, the lobby counter and what a ticker can and can’t tell you.
Ticker tabs each snapshot names, and the one we capture
A live wins ticker is a product feature. The casino picks which bets appear, how many tabs there are, whether player names show and whether losing bets appear at all. Every snapshot records those choices, because everything we measure starts from them.
- Several casinos run more than one ticker, and each snapshot says which one we capture. Gamdom has “Live Bets”, “High Rollers” and “Lucky Wins”. Only “Live Bets” is captured. “High Rollers” and “Lucky Wins” are marked “known-not-captured” and aren’t rebuilt. Cloudbet’s “Huge Wins” and “Biggest Payouts” tabs aren’t captured on their own either. Its snapshot marks them “calculated”, rebuilt from the captured “All Bets” feed, and “My Bets” is “private”.
- BC.Game publishes two feeds, “Latest Bet” (“captured-public-source-surface”) and “High Roller” (“captured-source-selected-positive-settlements”). “High Roller” is a selection of positive settlements, kept out of every cross-casino sum. 500 Casino’s snapshot names “All Bets”, “High Wins” and “Lucky Wins” as feed labels and marks “Royales” as “known-not-collected”. GOATED shows “Latest Bets” and “High Rollers” as separate tabs, and only “Latest Bets” is collected.
- A ticker can show a bet without showing who placed it. Gamdom flags each bet public or hidden. Of its 9,894,905 captured rows, 26.44% were hidden, and 4,716 source accounts are protected. An account with even one hidden row never enters an alias leaderboard. Roobet left 351,560 of 586,444 rows (59.95%) without a visible name. Its snapshot treats missing names and the literal “Hidden” as one protected group, never as one player.
- A ticker isn’t a head count either. CoinCasino shows a masked label on 91.78% of rows and carries no stable player ID. Shock shows a display name on 76.91% of rows and no stable account ID. Winna and Thrill show a username on some bets and no stable player ID, and Cloudbet marks 74.82% of rows public.
Every feed: surface, rows, rate, whole-feed ratio and its snapshot’s words
One row per casino. Each shows the surface we capture, what its feed publishes, its rows over its own seven-day window (Sep 16–23, 2026) and its snapshot’s completeness statement. We never add row counts across casinos.
- Rakebit and Whale.io publish only or almost only bets that paid out. Every captured row has a positive return except two of Rakebit’s 172,609, which returned nothing. You can’t read what was played, staked or lost from these feeds, so their rows count as published payouts, with no ratio.
- CoinCasino and Winna say in their own snapshots that the captured rows may be a selection. Winna’s snapshot says “may be selected or otherwise incomplete”. CoinCasino’s snapshot says “selection, masked-label concentration and large payout tails prevent casino-wide or person-level claims”. Their whole-feed ratio appears here as a fact about the feed, and the games page gives them no game-level ratio or net.
- DegenCity’s feed publishes settlements, not bets. 302,272 settlements have no visible parent bet in the window, so the feed has no complete stake total.
- Eight snapshots record feed completeness as “unknown” in a field of their own (AceBet, BetFury, Cloudbet, DegenCity, Gamdom, Roobet, Thrill and Winna). Another 10 carry a boundary sentence, quoted in the table, and Shock records none. No snapshot claims its feed is complete.
- Seven of the 15 USD-comparable feeds returned more than 100% of the stake they captured over the week: Winna 260.40%, CoinCasino 242.37%, Thrill 168.09%, Chips 147.12%, 500 Casino 117.64%, Gamba 114.46% and Gamdom 104.05%. One week is short, and a few big wins can lift any feed above 100%. The ratio describes the rows a ticker published, not what a casino pays.
- Rows per hour is a feed’s captured rows ÷ capture hours, the same math as the activity ranking. It is a feed rate, not a count of players or of every bet on the platform.
Pace and cadence: rows a second, silent minutes, longest silence, busiest minute
Each feed’s cadence over its own seven-day window: average rows a minute, minutes with a row, minutes without one, the longest silent run and the busiest minute. The collector’s own pauses come out before any minute counts as silent.
The pace behind each lane: rows captured ÷ the seconds the collector was running. Every window holds 166.5 captured hours, which is 168 hours minus the collector’s two pauses. The cadence table’s rows a minute divides by every full minute of the window, pauses included, so it reads slightly lower.
- The silent share runs from 40.6% at Roobet to 0.5% at GOATED, and the table is sorted by it. Each window holds 10,079 full minutes. Rows a minute is rows in window ÷ full minutes, an average over the window, not a live rate.
- Roobet’s ticker shows no row in 40.6% of its minutes. Its longest silence is 99 minutes, and its busiest minute holds 300 rows.
- Shock’s ticker shows no row in 17.3% of its minutes. Its longest silence is 36 minutes, and its busiest minute holds 93 rows.
- Short gaps next to big busy minutes mean a feed that publishes in batches. Its display refreshes in bursts, not one bet at a time. A long silence while the other 18 feeds carry rows belongs to that feed alone. Either its ticker showed nothing new or its endpoint returned nothing, and the capture can’t tell which. The longest is Winna’s, 170 minutes (Fri, Sep 18 02:58–05:48 UTC).
- Our collector paused on Thu, Sep 17 11:49–12:42 UTC (52.7 minutes) and Wed, Sep 23 18:01–18:37 UTC (35.5 minutes). Those pauses never count as silence, and the busiest-hours page lists them.
- The busiest minute in scope is Gamdom’s, with 3,309 rows at Sun, Sep 20 10:56 UTC. BC.Game’s figures leave 95,166 High Roller rows out of every count. In the snapshot’s words, “BC.Game’s High Roller rows (payloads with a gameInfoId) show only winning settlements. The BC.Game snapshot keeps them out of every total, and so does this page.”
When feeds are busiest, hour by hour, with the collector pauses
Rows grouped by the UTC minute of collected_at. A silent minute is a full minute inside the window with no row from this feed and no collector pause touching it. The longest silence is the longest run of silent minutes. Minutes with rows and the busiest minute count every in-window row.
The games each ticker displayed most
These are the eight games each ticker showed most, with each game’s share of that feed’s rows. The mix is the ticker’s, not the casino’s catalog.
- Keno17 of 19
- Plinko16 of 19
- Dice14 of 19
- Limbo12 of 19
- Mines10 of 19
- Blackjack9 of 19
- Crash4 of 19
- Fist of Destruction Megamultiplier3 of 19
- Sweet Bonanza 25003 of 19
- Wanted Dead or a Wild3 of 19
- coinflip2 of 19
- Gates of Olympus Super Scatter2 of 19
- Hilo2 of 19
- The listed games cover 8.2% of the feed at BC.Game, the least, and 100.0% at Qzino, the most. A list that covers nearly the whole feed means the feed shows little else. A small share means the rows spread across a long tail of titles. Qzino showed only seven distinct games in the window.
- Names match across feeds by spelling alone, ignoring case: Keno at 17 of 19, Plinko at 16 of 19, Dice at 14 of 19, Limbo at 12 of 19, Mines at 10 of 19, Blackjack at 9 of 19. The count is of feeds, never rows, and a name two feeds share isn’t verified as one title.
- A game leads because that ticker showed it most. The games page carries every board a feed published.
Most played games, casino by casino
Trimmed game_name, else trimmed game, else "Unknown game"
The currency label each ticker prints
For each feed, the column that carries the currency label, how many distinct labels it printed, the label on the most rows and the rows with no label.
- BC.Game prints the most currency labels, 145. 500 Casino (USD) and Gamdom (USD) print just one, the same label on every captured row. The feed doesn’t record whether a bet was placed in that currency or converted for display.
- USDT is the top label at 9 of 19 feeds, followed by SOL (3) and USD (3). Labels appear as each feed prints them (Roobet writes “usdt”), and we compare them across feeds ignoring case, nothing more.
- No feed in scope left a row without a label in this edition.
The lobby counter: samples, readiness and the snapshot’s words
Casino lobbies print a number beside each game. We sampled BC.Game’s lobby API and read that number exactly as served. BC.Game doesn’t document what it counts, and none of the bet feeds in scope carries a user counter.
- 4
- Sep 10, 2026 · 18 minutes end to end
- 12 · 6 h
- Samples, and the span they must cover
- collecting
- No ranking is published
- No
- BC.Game’s display number, read as served
The lobby snapshot, in its own words
- Source metadata: notes.counter
“onlineUsers is the number BC.Game’s own lobby prints on each game tile, read exactly as its lobby API serves it. 0xCasinos has not verified it, and BC.Game does not document how it is computed. It is not a count of players 0xCasinos observed.”
- Source metadata: notes.order
“The lobby’s default order is a recommender (recVersion values such as itemGames_None_default), not a popularity ranking. No server-side sort by players was found. 0xCasinos sorts by onlineUsers itself.”
- Source metadata: notes.coverage
“Third-party games are observed only inside the first 1,000 games of BC.Game’s own hot order (selection hot_games) in each sample. A game outside that slice is not observed, even if its counter is high. A sample in which a game is absent is missing data, not zero.”
- We read the number exactly as BC.Game’s lobby API serves it, with the User-Agent “0xCasinosResearch/1.0 (+https://0xcasinos.com/about)” and no cookies. BC.Game doesn’t document what it counts and we haven’t measured it, so we never call it a player count.
- The bet feeds carry no such counter. Gamdom’s snapshot records “onlineCountersAvailable: false” and Rakebit’s lists “Deposits, withdrawals, balances, bonuses, explicit free-spin state or online-player counts.” among what it didn’t observe. No bet-feed snapshot in scope publishes one.
- Our activity ranking divides captured events by capture hours. That makes it a feed rate, not people online. DegenCity, Rakebit and Whale.io lack a comparable set of completed events, so they get no position there.
What a ticker can and can’t tell you
Every measurement on this site starts with a ticker and shares its limits. Some readings hold up and some don’t.
What a ticker can tell you
Which games were on the board, and how often.
A game makes the games page because it was on a casino’s published boards. The count is that feed’s, never a total for the casino.
Most played gamesHow much a whole feed returned on what it captured.
Captured payout ÷ captured stake for one USD-comparable feed over one week. It describes the rows the ticker published, not a game’s RTP. Above 100% means the feed paid out more than it took that week. That comes from a few big wins, or from a feed that leaves out losing bets.
Payout ratio by casinoHow fast rows appear.
Events per capture hour, inside each feed’s own window. It ranks feeds, not casinos, and says nothing about players online.
Most active feeds
What it can’t
Not the casino’s turnover, revenue or house edge.
A ticker is a sample the casino chose to show. Nothing on this site scales it up to the whole casino, and no snapshot shows that a feed is complete.
What casinos don’t publishNot who is winning.
Names are hidden, masked or optional on the feeds that carry them. Several snapshots record no stable player ID at all, so a repeated name can’t be tied to one person.
Not what the next bet will do.
One week of one feed is a sample. Every casino game has a house edge, and a week where a feed finished ahead usually rests on a few big payouts.
How we read live wins ticker feeds, and what the page checks at build time
Every count is recomputed from the snapshots at build time. If a snapshot stops saying what we quote, the build stops.
Method
- Scope
- The 19 casinos in the current ranking scope, taken from the ranking contract, never listed by hand. Stopped collectors are out of scope. The newest snapshot is dated Sep 23, 2026, 21:27 UTC.
- Windows
- Each casino has its own capture window. The windows overlap but don’t match, so row counts are never added across casinos and every comparison is side by side.
- Quotations
- Every quoted sentence is read from its snapshot at build time and printed with the field it came from. If a figure depends on a sentence, like the two selection disclosures, the build stops when that sentence goes.
- Rows and rates
- Rows are each report’s event scope, the same figure the activity ranking uses, and the rate divides them by that report’s capture hours. Payout-only feeds count published payouts and the linkage-incomplete feed counts settlement rows. The unit is printed with the figure.
- Money
- A whole-feed ratio is printed only for USD-comparable feeds, and only as captured payout ÷ captured stake × 100. Payout-only feeds get no ratio, because a feed that leaves out its losing bets has no complete denominator.
- Counters
- The lobby figures come from the BC.Game lobby snapshot alone. Below its own readiness floor it publishes no ranking, and neither do we.
- Privacy
- No player name, alias or ID is read or shown. Hidden, protected and masked shares are the snapshots’ own aggregate fields.
Limits
- A public feed is not a ledger. The casino decides what its ticker shows, and a feed can leave bets out.
- A snapshot’s completeness field says what could be established, not what the casino does. “Unknown” is not “incomplete”.
- One week of one feed predicts nothing about the next bet. Every casino game has a house edge.
- We didn’t play these games, and our real-money tests are coming soon. Nothing here is a verdict on a casino.
- The lobby counter is one casino’s display number, read from 4 samples spanning 18 minutes.
More from the data
ResearchCrypto Casino Win Rates 2026: How Often Bets Pay, 13 FeedsCrypto casino win rates on 13 public bet feeds: 25.56% to 80.83% of bets paid out. See how many hit 10x, 100x or 1,000x and each feed’s biggest multiplier.
ResearchWhen Crypto Casinos Are Busiest: Bets by Hour at 19 FeedsSaturday is the busiest day at 9 of 19 crypto casino bet feeds. Peak hours, quiet hours and silent minutes for each feed, in UTC.
ResearchCrypto Casino Currencies 2026: What Bets Are Placed InUSDT leads 9 of 19 crypto casino bet feeds. BC.Game prints 145 currency labels and two feeds print only USD. Every label’s share of bets, feed by feed.