Our review of Frog Jump is based on hands-on play, not marketing copy. We loaded the official InOut Games demo, ran rounds, logged what each platform did to the multiplier, and cross-checked the numbers against the developer’s published spec. This page explains how we test and how we set a rating, so you can judge how much to trust our conclusions.
Where our facts come from
We use three kinds of source, in order of trust. First, hands-on testing: we play the demo and record what actually happens, like the platform-hop mechanic, the values each platform adds, and the fact that the round crashes to zero on a missed jump. Second, the developer’s own spec: InOut publishes the 95.5% RTP and the 23 June 2026 release date, and we treat those as authoritative. Third, aggregator and affiliate listings for figures the developer has not published, such as the exact bet range and the full flower values, and we label those clearly as unconfirmed rather than presenting them as fact.
What we verify hands-on
When we can check something in the game, we do. In testing we confirmed the $1,000,000 demo balance, that the stake is deducted the instant you press Play, the stone +0.05x, log +0.1x and lily-pad +1x values, the manual Cash Out button that stays on screen, and that a missed jump ends the round at zero. Where the game does not expose a detail, a full platform table, a hit-frequency figure, a public RNG certificate, we say it is unpublished. We do not invent it.
How we set a rating
Our score weighs the things that affect a real player: the return and volatility, the max win and how reachable it is, the quality of the core loop, the transparency of the spec, and the strength of the licensing. Frog Jump earned 7.6 out of 10, a genuinely tense, decent-RTP skill-crash game marked down for a thin published spec and a harsh risk profile. The rating is our opinion, formed from testing; it is not a guarantee of your results.
Corrections
Games change and figures get clarified. If we get something wrong, or if InOut publishes a detail we had to flag as unconfirmed, we update the page. You can flag an error through our contact page, and you can see who does the testing on the author page.