Advertising mode: editorial-only; no operator CTA or promotion.
NetEnt's game page publishes a theoretical RTP for Starburst, but the operator's available build and configuration should be checked in the game information panel.
Compare the operator’s exact version with the studio source. If it differs, do not assume the same configuration.
Quick comparison
| Detail | Studio page value | How to use it |
|---|---|---|
| Published RTP | 96.08% on NetEnt’s checked page | Long-run theoretical information for listed configuration |
| Reel layout | Five reels | Confirm rules for the displayed build |
| Features | Expanding wilds and respins described by studio | Read in-game rules for trigger conditions |
Steps to take
- Check the current information on the operator or provider.
- Confirm direction, account eligibility, currency and any stated limitations.
- Keep a non-sensitive reference and use official support if a question remains.
Original illustrations
Slot-mechanics diagram and abstract reel artwork.
Published figure
NetEnt's official Starburst page currently lists a published RTP of 96.08%. Treat this as information about the listed game configuration, not an expected return for a player, session or short series of spins.
Mechanics at a glance
Starburst is a five-reel video slot with expanding wild features and respins described by the studio. Read the in-game rules for the exact trigger conditions and symbol behavior in the version you are viewing.
Version matters
Operators can display a specific release, locale or configuration. Compare the game information panel with the studio source; if the values do not match, rely on the version-specific information shown for that game and ask the operator for clarification.
No prediction from RTP
RTP is a long-run statistical measure. It does not mean that a player will receive that percentage back, and previous spins do not determine the next result.
Frequently asked questions
Is 96.08% guaranteed to a player?
No. It is the figure shown on the studio page for the listed configuration and is not a session promise.
Can every operator version have the same RTP?
Do not assume so. Check the rules panel for the exact version presented.