Plinko

How the maths works

Each peg is a binary bounce. Outcomes follow a binomial distribution, so centre buckets are far more likely than edge buckets and pay accordingly.

Published RTP by operator

Published return to player for Plinko by operator

Casino	Plinko RTP	Evidence
Stake	99%	Operator states
Roobet	Not published	Not published
Rainbet	Not published	Not published
Duel	100% capped	Operator states
Shuffle	99%	Operator states
BC.Game	98%	Not published

Figures as published by each operator, last checked 2026-08-18. Where an operator does not publish a figure we say so rather than inferring one. Operators can change game configuration without notice.

What changes your results and what does not

Changes variance: risk settings, target multipliers, bet sizing, how long you play. All of these alter the shape of your outcomes, sometimes dramatically.

Does not change expected value: any of the above. On Plinko, as on every original, the house edge is constant across settings. A different configuration gives you a different distribution around the same expectation.

This is the point most strategy content gets wrong. There is no Plinko strategy that converts a negative expectation into a positive one, because the edge is applied to the payout formula itself rather than to any particular way of playing.

Verifying a result

Plinko runs on the standard provably fair model at every operator here: a hashed server seed committed before play, your own client seed, and an incrementing nonce. Rotate your seed to reveal the old one and you can reproduce every result it generated.

How to actually verify, and what it does not prove

Where to play it

Stake, Roobet, Rainbet, Duel, Shuffle, BC.Game

Check the published RTP in the table above before you choose. On several games the spread between operators is the largest cost difference available to you. Full RTP comparison