Jackpot Strike - Casino Slots

About Jackpot Strike - Casino Slots

Rather than building a new title from the ground up, the release uses Big Bass Splash 1000 as its base. The franchise’s signature Money symbol collection mechanic stays intact while a seasonal skin gets swapped in.

The headline mechanical difference is a shift in risk profile. This variant runs on a 5×3 grid with 10 paylines at an RTP of 96.50%, and the volatility has been eased to medium against the high-variance base game. That softens the swings while keeping the same top-end potential.

That ceiling stays substantial at 20,000x the bet. It’s reserved for a fully developed free spins round where Fisherman Wilds collect Money symbol values and progressive retriggers push collection multipliers higher.

What is Jackpot Strike - Casino Slots?

Once the deal is completed, 80% of its EBITDA is expected to come from those two markets.

According to the deal investor deck, the combined group expects online betting and gaming to be its largest vertical, as it accounted for 48% of the group’s combined pro forma adjusted EBITDA in H1.

Distributed gaming followed at 27%, then casinos at 25%.

About Jackpot Strike - Casino Slots

“The bottleneck becomes the person reviewing everything. That does not mean we never review the code itself. For sensitive or critical parts of the system, we still look more closely at the implementation, particularly from an architecture, performance, security and reliability perspective. But we no longer apply that level of manual code review to everything.” Grenstad says.

The shift to AI is also changing how Grenstad thinks about recruitment. A team working on the player journey, for example, needs people who understand casinos, iGaming and what a strong player experience should look like.

“I would not necessarily prioritise senior Java or front-end specialists in the same way as before,” Grenstad explains. “Technical skills remain important, particularly for people who can assess architecture and ensure systems remain reliable, but domain knowledge is becoming increasingly valuable. I’d rather take someone who’s good in the domain but doesn’t know any Java.”