Skip to content
LAB

Wheel

10-segment wheel with Low / Medium / High multiplier sets.

Wheel

10-segment wheel. Each risk profile has its own multipliers. floor(U · 10) → segment.

Bankroll
Bets0
Win %
Net P/L
Streak
Biggest win
Pick a risk profile and spin.
Presets
Auto-bet
How dishonest operators rig this game 3 documented tricks
01 Visual landing ≠ result

Mechanism. Wheel animation lands on a generous segment, then "shifts" 1–2 segments inward to the actual result. Implied as "natural deceleration".

Red flag. Compute the segment yourself from floor(U · N). The wheel must rest with the pointer ON that exact segment, not its neighbours.

02 Segment colour bait-and-switch

Mechanism. Big-multiplier segments are visually larger than their share. 9.9× segment renders 1.5× wider than other slots — player feels it's "achievable" but probability is 1/N.

Red flag. Count segments on the wheel image carefully. Equal pixel widths or it's manipulating perceived probability.

03 Risk-profile silent swap

Mechanism. During an auto-spin streak, operator changes risk profile mid-stream — same wheel image but different multipliers internally.

Red flag. Risk profile must be a committed parameter for the round, visible in PF data. Any "drift" between rounds = manipulation.

For the full compendium across all games, see The Book of Casino Dirty Tricks.

Server seed hash
Server seed (revealed after rotation)— pending rotation —
Client seed
Next nonce

The math behind each spin

Mathematical Audit Benchmark

How Does This Compare to 0% House Edge Protocols?

Audited 100% RTP

Instead of standard 1.00% to 4.00% casino house margins, compare with mathematically verified 100% RTP Originals (0.00% House Edge) on Duel Casino:

Duel 100% RTP Dice
100% RTP Dice: Exact 1:1 mathematical return (0.00% edge).
Duel VIP Rakeback
Instant VIP Rakeback: 0x wagering requirements with code Vip.

Wheel Mechanics and Odds
Wheel Random Distribution: Evaluating pocket probabilities and segment weights.

One HMAC float, one modulo step:

float    = uniform [0, 1) from HMAC bytes
segment  = floor( float · num_segments )       // 10 / 20 / 30 / 50 typical

The risk profile you pick fixes two things at once: how many segments exist and what the multiplier array looks like. Summed across all segments, expected value comes to (1 − house edge). Operators shape the array to land on that number precisely — segment count is where volatility gets tuned.

Low, medium, high: same EV, wildly different feel

The simulator’s defaults are honest. Low risk packs in 1.2× and 1.5× segments with zero 0× slots; medium sprinkles in a few 2× and 3× multipliers next to several 0× slots; high risk compresses everything into one 9.9× slot and fills the remainder with zeros.

That high-risk wheel is an emotional trap. A 9.9× slot looks reachable — until you notice it shares the wheel with nine wipeouts. Expected return matches low risk exactly. Variance is roughly 10×.

When the animation lies about where it landed

There’s a known manipulation pattern with wheels: the spin visually touches a fat multiplier, then eases one or two segments back “organically” to the real result. It works because nobody can count segments accurately on a wheel mid-spin.

Test. Pull a real round from an operator into the wheel verifier. The math-derived segment must sit under the pointer once the wheel stops moving. Any drift means the animation is theater.

Frequently asked questions

What’s the maximum multiplier on this game?

It varies by risk profile and operator. Stake’s classic High wheel carries a single 9.9× slot; some operator variants stretch to 49× or 99×. Read the displayed multiplier array before betting anything.

Can the wheel have hidden segments?

No — segment count is fixed and visible. The operator could still misreport it in the UI, though. Check it yourself: compute floor(float · N), where N is the count you can literally see on the wheel image. A match means the drawn wheel agrees with the math.

Why does the high-risk wheel feel like it’s “hot” sometimes?

It isn’t. Every spin stands alone. What happens is that 1-in-10 outcomes occasionally cluster, and clustered wins read as a streak. Feed 100+ spins into a streak analyzer — the clustering should fit i.i.d. 10% events.