Stake Slide Live Stats: How Our Tracker Reads the Carousel Stops
By LiveCasinoData editorial team · Updated 2026-08-28 · 14 min read
Our Stake Slide tracker stores the exact value the multiplier carousel stops on for every round, 2,277 rounds since capture began on 2026-08-27. The live page groups those stops into five buckets and tracks gaps between big ones, and the shares observed so far sit within about a point of the 0.99/x model that also describes Stake Crash. The dataset is only about a day old, so every figure on this page is an early reading, not a settled long-run number.
Key takeaways
- The tracker at /games/stake-slide stores the single value the multiplier carousel stops on for each round, sorted into five buckets: under2, 2to5, 5to10, 10to50 and over50.
- As of 2026-08-28 the tracker holds 2,277 rounds spanning roughly 23 hours, all captured since the game was added on 2026-08-27, so bucket shares are still an early reading.
- Observed bucket shares (under2 49.63%, 2to5 30.13%, 5to10 9.44%, 10to50 8.78%, over50 2.02%) sit within about a point of the theoretical 0.99/x model shared with Stake Crash.
- The overall average stop is 9.09x, but that number is pulled up by rare large stops; the median of 2.01x describes a typical round far better.
- The round-level RTP field averages 95.03% but has a median of just 41.98%, because a Slide round's realized payout depends entirely on how many individual bettors' own targets happened to clear, which makes that field far noisier than a crash multiplier average.
Stake Slide settles by a carousel of multiplier cards scrolling to a stop, not by a wheel, a dealer, or a rising curve a player watches and reacts to, and our tracker records that single stopping value the instant a round settles. As of 2026-08-28 that is 2,277 rounds, captured since the game joined our tracker on 2026-08-27, covering roughly the first 23 hours of data. This page walks through what a stored Slide round actually contains, why one field in that record is far noisier than you might expect, how to read each panel on the live page, and what that first day of results shows. For the mechanics of choosing a target and reading the carousel itself, see the how-to-play guide.
What does the Stake Slide tracker actually record?
A stored round holds the exact value the carousel stopped on, to two decimal places, the bucket that value falls into, and that round's own realized payout percentage across everyone who bet in it.
The raw feed behind Slide is multiplayer, the same as most Stake Originals titles: it lists a bettor count, a winner count, total amounts staked and paid out, and a winners array naming each winning bettor's own target multiplier and payout. None of that per-player detail reaches our database. What we keep is the round-level outcome, pulled from the feed's data.result.maxMultiplier field, which always appears among the roughly 90 individual card values carried in that round's data.numbers array. The multiplier column holds that stop value, the result column holds the bucket key, and a result_details field adds the same stop value under crash_multiplier, the bucket label, and round_rtp, that round's realized payout share.
One gap is worth flagging: our schema has a round_duration_ms field, but it comes back empty for every Slide round captured so far, since the feed does not populate it for this game. The pacing figures here instead come from each round's start and settle timestamps: a carousel run of roughly 5.5 seconds, inside a full round cycle of about 37 seconds. That is slower than Stake Crash's roughly 27 to 28 second pace, which fits the mechanics: Slide has no live reaction window to wait through, but it still spends time displaying the carousel scrolling and settling before the next round opens.
The stop value itself is grouped into the same five ranges used across the site's multiplier-style games, so the numbers can drive familiar widgets:
- under 2x, the most common outcome by a wide margin
- 2x to 5x
- 5x to 10x
- 10x to 50x, flagged in our data as a "big win" round
- 50x and above, also flagged as a big win
The stored multiplier value is the carousel's stop, not a payout to any specific bettor. Every player locks in their own target before the round starts, and win or loss depends purely on whether the stop landed at or above their number. A round stopping at 3.40x pays every bettor whose target was 3.40x or lower and nothing to anyone who set a higher target; our database has no visibility into which targets were actually chosen.
How is Slide different from a wheel game and from Stake Crash?
Slide comes from Stake, a Curacao-licensed operator whose in-house Stake Originals studio builds titles like this one, and there is no live dealer, no camera feed and no physical randomizer behind any of it, unlike wheel-based shows such as Crazy Time or Monopoly Live.
The closer comparison, and the one readers most often ask about, is Stake Crash, Slide's sibling under the same Stake Originals provider profile. The two share a similar house edge, but the decision structure is opposite. Crash gives a player a live multiplier climbing in real time and a cash-out button they can press at any moment before it stops, so the outcome depends on both the eventual crash point and the timing of that reaction. Slide has no such moment. A player fixes a target multiplier before the carousel starts moving, and from there the round's result is entirely mechanical: stop at or above the target wins the target's payout, stop below it loses. Readers coming from Crash expecting a rising curve and a cash-out prompt will find neither on Slide.
That distinction is why this page treats Slide's "reaction time" question as moot, while Stake Crash's live-stats page spends real space on cash-out timing. It also separates Slide from other RNG multiplier titles on the site: Evolution's Cash or Crash keeps a live host and studio setup around its crash mechanic, and Lightning Dice is another RNG-driven multiplier game with its own odds model. None of the bucket shares or gap figures below should be read across to those titles.
How do I read each panel on the live page?
Every widget on /games/stake-slide describes stops that have already happened; none of them forecasts where the carousel lands next.
Live results strip. Lists the most recent stops first, each tagged with its value and bucket, useful for confirming what a round you just watched actually settled on.
Bucket shares panel. Compares how often each of the five buckets has actually landed against the theoretical share implied by the 0.99/x model, over whatever window is selected.
Biggest stops panel. The largest carousel stops recorded in the window, with dates attached, useful for context on how rare a 100x-plus stop is rather than as a sign another one is close.
Drought and gap tracker. Counts rounds since a 10x or 50x threshold was last cleared, alongside the average and longest gap on record. It measures elapsed time only; it has no bearing on how long the next wait will be.
Probability calculator. Enter a target multiplier and a round count, and it returns the chance of at least one stop reaching that target across that span, computed from the fixed survival curve rather than from history, making it the one genuinely forward-looking panel on the page.
Hot and cold panel. Flags buckets currently landing above or below their expected share. Purely descriptive; a bucket running warm carries no extra weight for the next round, and a cold one is not due for a correction.
What do the bucket shares show after the first day?
The five buckets already track the 0.99/x theoretical model closely, with no bucket off by more than a point.
| Bucket | Theoretical share | Observed rounds | Observed share | Difference |
|---|---|---|---|---|
| under2 | 50.50% | 1,130 | 49.63% | -0.87 |
| 2to5 | 29.70% | 686 | 30.13% | +0.43 |
| 5to10 | 9.90% | 215 | 9.44% | -0.46 |
| 10to50 | 7.92% | 200 | 8.78% | +0.86 |
| over50 | 1.98% | 46 | 2.02% | +0.04 |
The over50 bucket, the smallest sample at 46 hits, lands closest to theory of the five, which is more a reminder that small samples wobble in both directions than evidence the game is running true to any particular decimal. This same 0.99/x survival curve is the model used for Stake Crash, and the fit here is one reason our facts pack leans toward the 99% RTP figure Stake's own game configuration states, over the 98% some third-party guides cite; a single day of data is not enough to settle that dispute on its own.
Why is the per-round RTP field so much noisier than the multiplier average?
Because a Slide round's realized payout depends on how many separate bettors' own targets happened to clear that round, not on a single climbing curve like Crash, the round_rtp field swings far more than the stop value itself does.
Averaged across all 2,277 rounds, round_rtp comes out to 95.03%, close enough to Stake's published figure to look reassuring at a glance. But the median is only 41.98%, and the range runs from 0.0% (every bettor's target missed) to 2,930.53% (a cluster of bettors all cleared their target at once). A crash game's round-level RTP tends to cluster near the published figure because one curve and one crowd of cash-out decisions produce a relatively smooth outcome. Slide's depends instead on the mix of targets bettors happened to choose that round, which can swing from near-total loss to a payout many times the stake pool. Treat the 95.03% average as a side statistic, not confirmation of either RTP figure in circulation; the bucket-share match above is the steadier evidence.
How do stop values behave within each bucket?
Inside every bucket the stop value skews toward its low end, and that skew sharpens the higher the bucket.
| Bucket | Average stop | Median stop |
|---|---|---|
| under2 | 1.37x | 1.33x |
| 2to5 | 3.06x | 2.89x |
| 5to10 | 7.04x | 6.74x |
| 10to50 | 20.54x | 16.95x |
| over50 | 248.47x | 98.43x |
The over50 bucket makes the point clearest: a median of 98.43x sits well below the 248.47x average, which is being pulled upward by a small number of exceptionally large stops rather than describing a typical round in that bucket. Across all 2,277 rounds, 246 (10.8%) reached 10x or higher, 46 (2.0%) reached 50x or higher, 22 (1.0%) reached 100x or higher, and just 1 (0.04%) reached 1,000x or higher. The largest stops recorded so far appear below.
| Rank | Stop value | Date |
|---|---|---|
| 1 | 4,987.48x | 2026-08-28 (overnight) |
| 2 | 576.73x | 2026-08-27 |
| 3 | 502.22x | 2026-08-28 |
| 4 | 401.98x | 2026-08-27 |
| 5 | 308.33x | 2026-08-27 |
| 6 | 281.82x | 2026-08-28 |
| 7 | 238.23x | 2026-08-27 |
| 8 | 227.76x | 2026-08-27 |
Why does the 9.09x average overstate what a typical round looks like?
Because the overall average stop, 9.09x across all 2,277 rounds, is dragged upward by a handful of rare large stops, while the median, 2.01x, sits far closer to what most rounds actually produce.
This follows from the shape of the underlying distribution, not from anything specific to this sample. If Slide's stop point follows the same 0.99/x survival model that fits Stake Crash, P(stop at or above x) = 0.99 / x for any x of 1x or higher, which means the probability of clearing a very high target shrinks slowly enough that the rare huge stop still contributes disproportionately to a running average. One round out of 2,277 has cleared 1,000x, and that single stop alone visibly lifts the mean above where the bulk of rounds actually land. The 90th percentile stop across the full dataset is 10.74x, meaning nine out of ten rounds so far have stopped below that mark, a far more grounded reference point than the mean.
That same survival curve sets the odds for any fixed target a player might choose:
| Target multiplier | P(stop reaches target) |
|---|---|
| 2x | 49.5% |
| 5x | 19.8% |
| 10x | 9.9% |
| 50x | 1.98% |
| 100x | 0.99% |
| 1,000x | 0.099% |
Because a Slide bet wins whenever the stop is at or above the chosen target, that survival probability is also the win chance for a target set to that value. The expected value works out to roughly -1% under the 99% RTP figure our configuration states, or -2% if the 98% figure some guides cite turns out to be correct, and either way it is identical at every target: setting a low target near 2x wins often for small payouts, and setting a high target near 50x wins rarely for large ones, but neither carries a mathematically better edge than the other. Choosing your target is the entire game, and the tradeoffs behind that choice are covered in Choosing Your Target Multiplier.
What do the gaps between big stops look like?
A drought here counts rounds since the carousel last cleared a threshold, and so far the average wait is 9.3 rounds for a 10x-or-higher stop and 48.2 rounds for a 50x-or-higher stop, with longest observed gaps of 94 rounds and 128 rounds respectively.
Those figures are consistent with independent rounds rather than any streaky pattern. A 9.9% per-round chance of clearing 10x means a 94-round gap without one is unusual but far from impossible across 2,277 attempts; the same logic covers the 128-round gap on the rarer 50x threshold. Nothing about a long gap raises the odds that the next round clears the threshold, because each stop is generated fresh by the same server-seed-and-nonce process Stake uses across its Originals catalog, verifiable after the fact through the client's fairness panel rather than by watching for a pattern in past stops. Treating a long gap as a sign a big stop is "due" is the same reasoning error whether it is applied to a wheel segment, a crash point, or a carousel stop, and Slide's provably fair verification, not any streak reading, is the actual way to confirm a round was fair.
With only about a day of history behind these figures, expect both the average and longest-gap numbers to shift meaningfully as more rounds accumulate, particularly on the over50 threshold where 46 total hits is still a thin sample. The strategy guide covers why chasing a drought by raising bet size does not change the underlying edge, no matter how long the current wait has run.
How do I check today's Stake Slide results?
Open /games/stake-slide and read the live results strip, which lists each new stop as the round settles, roughly every 37 seconds around the clock.
There is no fixed daily results page to publish for a game that runs continuously; any number printed on a page like this one would be stale within a minute of a new round settling. Because the tracker currently holds only about a day of history, its full dataset and its rolling 24-hour window cover close to the same rounds, so the figures above should match what the live page shows closely for now. That overlap will shrink as more days of data accumulate and a single day becomes a smaller slice of the whole.
How reliable is this data, and what should I keep in mind?
The tracker is young, about a day of coverage as of 2026-08-28, so every share and gap figure on this page is an early reading rather than a settled long-run number, and the same caution applies to the 98% versus 99% RTP question this facts pack flags as unresolved.
Two structural limits matter beyond sample size. First, our database keeps the round-level stop value, its bucket, and the round's realized RTP only; it does not retain individual bettor targets, wager sizes, or how many players were in a given round, all of which the raw feed carries but we discard. Second, the round_duration_ms field is simply not populated for Slide, so any per-round timing figure on this page comes from timestamp arithmetic rather than a stored duration value, a gap specific to how this game's feed is structured.
None of that changes the direction of the first day's numbers: bucket shares tracking the 0.99/x model within a point, a median stop of 2.01x that represents a typical round far better than the 9.09x average, and gap behavior consistent with independent, provably fair rounds. No fixed target carries a better theoretical edge than any other, the carousel has no memory of its last stop, and a long gap without a large stop is not a signal one is coming. Treat Stake Slide as entertainment with a budget decided in advance, not a way to grind out a profit. See the Stake Slide RTP page, the site-wide RTP monitor, the fairness index, and the responsible gambling observatory for the wider picture.
Frequently asked questions
What is Stake Slide and how does our tracker record each round?
Stake Slide is a Stake Originals game where a carousel of roughly 90 multiplier cards scrolls and slows to a stop on one final value; a bet wins if that value is at or above the target multiplier the player picked before the round began. Our tracker stores that single stop value from the feed's result.maxMultiplier field, plus the bucket it falls into and the round's own realized payout percentage.
How many Stake Slide rounds does the live tracker have?
As of 2026-08-28 the tracker holds 2,277 rounds, all recorded since the game was added on 2026-08-27. That covers roughly the first 23 hours of coverage, so bucket shares and gap figures, especially for the smaller over50 bucket with 46 hits so far, will keep moving as more rounds accumulate.
What is the highest Stake Slide multiplier recorded so far?
The highest carousel stop our tracker has captured is 4,987.48x, recorded overnight on 2026-08-28. The next largest are 576.73x and 502.22x. Only one of the 2,277 rounds tracked so far, about 0.04%, has stopped at 1,000x or higher, which is why a single huge stop can dominate the running average without describing a typical round.
Can the tracker predict where the Stake Slide carousel will stop next?
No. Each stop is generated independently and verified through Stake's provably fair process, so a long run of small stops does not make a large one more likely on the next round. The tracker's hot/cold, drought and pattern panels describe what already happened across 2,277 rounds; they do not forecast round 2,278.
Where can I see today's Stake Slide results?
Open /games/stake-slide and read the live results strip, which lists the newest stops as rounds settle, roughly every 37 seconds. There is no separate daily results page because the game runs continuously; with only about a day of history right now, the tracker's full dataset and its 24-hour window cover close to the same rounds.