candy-wave
- RTP
- 97.00%
- Volatility
- HIGH
- Max win
- 10,000×
- Hit freq
- -
- Grid
- -
- Bet
- -
- Released
- 2026-01-12
A playable demo is not available in your region.
Our take
97% RTP crash game with 10000× max, rising multiplier waves, and timing-driven mechanics from Capecod Gaming.
Candy Wave by Capecod Gaming is a crash-style instant game, not a traditional reel slot, wrapped in a bright candy-and-trolls aesthetic. Players watch a multiplier wave rise across the screen and choose the moment to cash out before it crashes. Miss the timing and you lose the stake; time it right and you pocket the current multiplier value.
The gameplay is pure skill and timing rather than spin luck. Random multiplier spikes can create sudden surges or sharp drops, keeping decision-making tense across each round. The 97% RTP is high for its class, signalling fair house edge even though the play pattern is entirely different from traditional slots.
Visuals flip between cheerful (sweets, lollipops, cakes, trolls) and high-risk tension (the crash moment itself). The contrast makes the gameplay feel less oppressive than typical crash games, though the mechanics remain identical: rise, time, crash.
Pros
- 97% RTP is the highest in this review batch
- 10000× max exposure offers extreme upside for timing experts
- Skill-driven timing provides gameplay variety vs. pure chance
Cons
- Crash mechanics are not traditional slots—a learning curve for classic players
- High max win is rarely reached; timing precision required
- Fast rounds can feel frantic and mentally taxing
Math & maxes
Math breakdown
- Volatility score
- 3 / 5
- Max win
- 10,000x the stake
FAQ
What is the RTP?
97%, among the highest available in crash games.
How do I win?
Watch the multiplier rise and cash out before the wave crashes; larger multipliers mean larger wins.
What is the max win?
10000× your stake if you time a maximum wave correctly.
Is it skill-based?
Yes—timing your exit is the core skill; random spikes add unpredictability.
Can I set auto-play?
Crash games typically require active decisions; check your operator for auto-exit thresholds.

