No free demo for this gameGambleLex shows only demos served by the game’s own provider.
Pineapple Play3 games on GambleLex
Midnight Mirage
6-reel video slot by Pineapple Play with 96.42% RTP and high volatility, released 2026.
- RTP
- 96.42%
- Volatility
- High
- Max win
- 25,000×
- Reels × rows
- 6×5
Sources disagree
HighReview site
Medium-highReview site
19 facts from 2 sources, captured 10 Oct 2026. Sources differ on 3 values.
Game details
- Bet range
- 0.10–100Stake per spin
- Release date
- 8 Apr 2026
- Type
- Video slot
- Technology
- HTML5, JS
Sources disagree
0.10–1002 review sites
Max bet 800Review site
Sources disagree
HTML5, JSReview site
HTML5Review site
Not reported by any source: paylines and hit frequency.
Features
- Free spins
- Bonus game: no
- Wild symbol
- Progressive jackpot: no
Also listed by sources
- Additional free spins
- Reels doubling
- Splitting symbols
- Bonus bet
- Synchronizing reels
- Reelset changing
- Scatter symbols
- Buy feature
- Scatter
Theme
- Luxury
- Urban
- Car
- Cocktail
- Neon
Platforms: Desktop, Mobile
Where to play Midnight Mirage
No casino lobby captures for this game yetGambleLex lists a casino here only after seeing Midnight Mirage in that casino’s own game lobby.
About Midnight Mirage
What is the RTP of Midnight Mirage?
Most sources give 96.42%.
Can I play Midnight Mirage for free?
GambleLex has no demo from the provider for this game yet.
More from Pineapple Play
All 3 Pineapple Play 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 |
|---|---|---|
| Volatility | No majority | HighReview siteMedium-highReview site |
| Bet range | No majority | 0.10–1002 review sitesMax bet 800Review site |
| Technology | No majority | HTML5, JSReview siteHTML5Review site |
Sources
- ↑ SlotCatalog. Captured 10 October 2026.
- ↑ Chipy. Captured 10 October 2026.
All 19 reported facts with their sources
Published Updated Report a correction