Winning numbers
Red —
Black —
Zero —
◆ Commitment
Waiting…
Live table paused
You are still signed in.
Round, result and chat updates are sleeping to save server resources.
Tip Tap centres, dividing lines or intersections—every native roulette bet is live.
Sign in to play
●—
On the felt
●0
The easiest way to test your roulette system.
Test simple or complex roulette systems with flow charts, betting triggers and a drag-and-drop editor. Free forever. No coding required.
Start your own system, or explore the examples below to see what you can build.
New systemFree forever
Build your first betting trigger
Use plain-English choices to define when the system acts, what it bets and how the stake changes. No coding is needed.
- 1Add a triggerChoose the event and conditions
- 2Set the betPosition, stake and table limits
- 3Run the testChoose spins and review performance
Spin choices: fresh server-generated spins, results you paste, or administrator-approved server verification for shareable proof. Run up to 250,000 spins and review profit or loss, bankroll, drawdown and every decision. Private building and testing is free forever.
Optional shortcutStart from an example systemBrowse pre-built systems only if you want a starting point. Your own idea remains the main path.Browse examples
Editable examples
Choose a starting point
Every example is editable. Saving creates your own private copy.
New roulette system
Start with one trigger.
More
+
Start here
Create your first trigger
Tell the tester when to act. Then it will ask what to bet, how much to stake and where to stop.
System flow
Select a block to edit. Drag triggers to reorder.
So farChoose when this trigger should run
Choose when this trigger should start.
More triggers and grouped logic 0 triggersBuild nested logic blocks, dependencies, cooldowns and ordered bet actions+
WHEN→ALL / ANY blocks→ADD / REPLACE / SKIP
Start with one plain-language block. Add another only when a rule needs brackets, alternatives or a separate exception.
Add groups and rules to see how decisions will be evaluated.
Ready to check
Save or select Check rules for server-authoritative validation.
Private spin source
Import spin results
Paste numbers 0–36. They stay in this tab until you run a private test, then are sent securely for that test and removed from the server job when it finishes.
Completed simulation
Results
Ending bankroll—After the completed test
Net result—
Return on amount bet—
Bankroll balance
Balance Starting bankroll
This unlisted run is calculated by the protected server engine. It is not published as certified proof.
More run statisticsDrawdown, stakes, limits and spin counts
Spin-by-spin decision trace
| Spin | Result | Decision | Stake | Returned | Balance |
|---|
The proving ground
Systems, ranked by receipts.
Compare long-run play, not lucky screenshots. Observed edge is historical return on amount wagered.
10,000+spins for
a serious sample
a serious sample
Highest bankroll—Current player systems
Best observed edge—minimum 500 spins
Most tested—spins logged
| Rank | Player / system | Bankroll | Observed edge | Spins | Avg bet | Net result |
|---|
Observed edge = net winnings ÷ amount wagered. It describes past results and does not demonstrate a predictive advantage.
Every spin can be checked
See why the result cannot be changed.
The server does not send players an encrypted winning number. Before betting, it keeps a private one-time code and shows everyone a safe fingerprint of that code. After betting closes, the code and winning number are revealed so anyone can check they match the earlier fingerprint.
The result is locked
The server creates a new private code for the round. It shows everyone a safe fingerprint of that code before any bets are accepted. The fingerprint cannot reveal the winning number early.
Fingerprint shown before betsWaiting for round data…The code stays private
Players place bets while the timer runs. When time is up, betting stops. The server uses its locked code to produce the result; the wheel animation only displays that result.
03215194
Everyone gets the proof
The server reveals the one-time code and winning number. Your browser can check both against the fingerprint shown before betting, so a changed result would fail the check.
One-time code revealed after betsShown after the spin finishesTechnical details, if you want them
The fingerprint is a SHA-256 commitment made from the round number and a fresh 256-bit secret. After betting closes, the result is derived with unbiased rejection sampling. The revealed secret lets any browser reproduce both the fingerprint and the winning number. The wheel animation never chooses or changes the result.
Check it yourself
Check the latest spin
When a spin finishes, your browser can compare its public proof with the fingerprint shown before betting.
◇Waiting for a finished spinThe proof appears after betting closes