No free demo for this gameGambleLex shows only demos served by the game’s own provider.
Fluxberry
5-reel video slot by Tom Horn Gaming with 92.09% RTP and low volatility, released 2022.
- RTP
- 92.09%
- Volatility
- Low
- Max win
- 1,670×
- Reels × rows
- 5×4
1 other value
92.09%3 review sites
95.09%Review site
1 other value
5×42 review sites
4×5Review site
22 facts from 4 sources, captured 8–10 Oct 2026. Sources differ on 4 values.
Game details
- Paylines
- 40
- Bet range
- 0.50–100Stake per spin
- Release date
- 1 Jun 2022
- Type
- Video slot
- Technology
- HTML5
1 other value
0.50–1004 review sites
Min bet 0.10Review site
Sources disagree
HTML5Review site
HTML5, JSReview site
Not reported by any source: hit frequency.
Features
- Free spins
- Bonus game: no
- Wild symbol
- Progressive jackpot: no
- Autoplay
Also listed by sources
- Bonus round
- Mobile
- Multiplier
- Scatter
- Walking symbols
- Moving wilds
- Expanding symbols
- Locked reels
- Scatter symbols
Theme
- Fruits
- Retro
- Fruit Machines
- Berries
- Raspberries
Where to play Fluxberry
About Fluxberry
What is the RTP of Fluxberry?
Most sources give 92.09%. review site gives 95.09%; slots often ship in several RTP versions.
Can I play Fluxberry for free?
GambleLex has no demo from the provider for this game yet.
More from Tom Horn Gaming
All 105 Tom Horn Gaming gamesSources and dates
Every value on this page comes from a dated source capture. When sources give different values, the value most sources give is shown first.
Where sources differ
| Value | Most sources | Also reported |
|---|---|---|
| RTP | 92.09%3 review sites | 95.09%Review site |
| Reels × rows | 5×42 review sites | 4×5Review site |
| Bet range | 0.50–1004 review sites | Min bet 0.10Review site |
| Technology | No majority | HTML5Review siteHTML5, JSReview site |
Sources
- ↑ Casinolandia. Captured 8 October 2026.
- ↑ VegasSlotsOnline. Captured 9 October 2026.
- ↑ Chipy. Captured 10 October 2026.
- ↑ SlotCatalog. Captured 9 October 2026.
All 22 reported facts with their sources
Published Updated Report a correction