Sparkling Fresh by Endorphina: five-line rules and Scatter paytable

Sparkling Fresh is a five-reel, three-row fruit slot with only five paylines. Endorphina publishes 96.01% RTP, medium-low volatility and a €0.05–€200 supplier stake range. Stars act as Scatter, while the classic Risk Game is the only additional core feature listed.

The official page was checked on 8 October 2026. These supplier facts do not confirm New Zealand operator availability, NZD stakes or an identical deployed build.

Published configuration

Field	Official value
Grid	5×3
Paylines	5
RTP	96.01%
Volatility	Medium-Low
Supplier range	€0.05–€200
Scatter	Star
Five-Scatter pay	50× base bet
Other listed feature	Risk Game
Bonus Pop	Official FAQ says no

Five paylines make the geometry easier to inspect but do not make every horizontal group a win. Open the live line map and trace the highlighted combination from the first reel.

Star Scatter rules

The provider says three or more Stars produce a win, and five Stars pay 50 times base bet. The current page does not list a Free Games feature. Do not turn the Scatter award into free spins simply because that is common in other slots.

Capture the full grid and number of Stars. Use the paytable to identify the award for three or four, as the public excerpt gives the five-symbol example only. The round record is stronger than a celebratory animation.

No documented Wild or Free Games

The official core-feature list does not include a Wild, Free Games or Bonus Pop. This matters. A useful review reports the compact design as it exists rather than adding generic sections that imply unavailable mechanics.

If a live build displays an extra control, record its game ID and help page. Treat it as deployment-specific evidence until reconciled with the supplier source. Fruit symbols and stars alone do not prove a hidden bonus.

Fruit and seven paytable

The seven is the highest-paying regular symbol and awards 1000 times base bet for five on a valid line. Watermelon and plum are equal second-highest at 100x for five. Other fruits require the live table.

The 1000x entry is not a stated title-wide win cap. It belongs to one five-symbol line. Convert it to money only after establishing base bet, total stake and denomination.

Five-line arithmetic

With five lines, an interface may show line stake prominently. Multiply only according to the game’s displayed total. A €0.05 supplier minimum may correspond to one cent per line in one build, but that relationship must be observed rather than assumed.

Create a simple record: line number, symbol count, table multiplier, base-bet unit and award. When several lines win, add their server-recorded results once. Do not count Scatter awards as ordinary left-to-right lines unless the paytable explicitly does so.

RTP and medium-low volatility

The published 96.01% RTP is a theoretical long-run percentage. It cannot promise a result in one session. Medium-low volatility describes relative distribution, not an assurance of frequent wins or a fixed interval between Stars.

Save the live RTP, game ID and version. If a different percentage appears, retain both dated sources and identify which build each describes. Never average the numbers.

Stake and currency boundaries

Endorphina lists €0.05–€200. This unusually broad euro range is not an NZD promise. Operator limits, denomination steps and local access must be checked after login.

Confirm the final monetary total before each spin, especially when changing coin value. A five-line layout does not make the maximum stake appropriate. Set time and loss limits independently of the visual simplicity.

Risk Game

The Risk Game exposes an existing award to a new outcome. It can reduce or remove the original credit. Preserve the win before risk, amount exposed, selection, result and final balance.

If partial risk is possible, record the protected and exposed portions. If the feature is disabled, the base game’s published RTP may still require its own live confirmation; do not infer a change without help-page evidence.

Mobile and demo checks

Endorphina says the game supports mobile devices. Test whether all five lines, Star count, stake and Risk Game decision fit portrait mode without overlap. Colourful fruit should not be the only way an outcome is communicated.

The official demo can teach controls and line geometry. It does not prove a New Zealand operator carries the title or uses the same stakes. Keep demo observations labelled accordingly.

Worked line example

Suppose five sevens align on an enabled payline. Record the line number and verify that all positions follow the published path. Copy the game’s base-bet definition before applying the 1000x table entry. Then compare with the currency credit.

If five sevens appear on mixed rows without one enabled route joining them, the visual count alone is insufficient. Conversely, a zig-zag line may pay even when symbols are not on one horizontal row.

Worked Scatter example

For a three-Star stop, capture all positions and the specific Scatter award from live help. Do not search for a left-to-right line unless the help requires one. For five Stars, compare the 50x base-bet entry with the server result.

The Star award and any ordinary fruit line can occur in the same round. List them as separate components, then confirm the combined total. This prevents either omission or double counting.

Common mistakes

One error is claiming that three Stars trigger Free Games. The official page says they win, but does not publish free spins. Another is inventing a Wild. A third is calling 1000x a confirmed maximum win for the game.

Players may also treat €200 as a sensible or locally available stake. It is only the supplier range endpoint. Finally, medium-low volatility should not be translated into “safe” or “predictable”.

Evidence pack

Keep UTC time, operator, title, game ID, version, RTP, currency, denomination, total stake, balances, grid, Star count, line map, highlighted wins and final credit.

For the Risk Game, add the original award and decision chain. Redact personal information before sharing evidence, but retain original files privately.

Building the five-line map

Copy the five routes from live help into a simple numbered diagram. Mark the row occupied on each of the five reels. For every ordinary win, record the line number rather than saying the fruit “went across”. This makes zig-zag combinations reproducible and prevents a visually straight group from being paid when it is not enabled.

The compact map is also useful on mobile, where line animations may run quickly. A static reference lets a reader compare the stopping grid with the rule after the animation ends. If the operator allows individual lines to be disabled, record the active set; otherwise state that the live build fixes all five.

Reading Scatter and line awards together

Star Scatter evaluation should be kept separate from fruit and seven lines. Create one row for each line award and a final row for the Star result. The round total should equal those server-recorded components, subject to the exact base-bet unit shown in help.

This matters when a Star shares a visual path with fruit. The Star does not become the missing fruit unless a Wild rule exists, and none is listed. Conversely, a Scatter award may be valid without a left-to-right line. The detailed table—not colour, splash size or celebratory sound—defines each component.

Questions for support

Ask which RTP build is active, how base bet maps to the five lines and how three- and four-Star awards are calculated. Request a line-level breakdown for any disputed seven or fruit combination.

If a live screen shows an unlisted feature, provide its game ID and ask whether it is a separate version. For unavailable access, ask for the territory rule rather than citing the demo.

For a Scatter dispute, request the count, positions, paytable row and base-bet value used by the server. This is more precise than asking why a bonus did not start, because the current source does not document a bonus round. For an ordinary line, request the numbered route and symbol count so the five-line map can be checked directly.

Short answers

How many paylines are there? Five.

What is the Scatter? The Star.

Do Stars trigger Free Games? The current official page describes Scatter awards, not Free Games.

Is there a Wild? None is listed in the current core features.

What is the top listed regular symbol? The seven, at 1000x base bet for five.

Does the game have Bonus Pop? The official FAQ says no.

Final assessment

Sparkling Fresh is a genuinely simple five-line title. Its review value comes from resisting generic assumptions: Stars pay as Scatters, the Risk Game is separate, and no Wild or Free Games are documented on the current page.

Confirm the live line map, RTP and total stake. A small evidence table is enough to make each result understandable without adding unsupported features.

Official and related sources

• Sparkling Fresh official product page
• Endorphina catalogue guide
• Responsible gambling guide
• Corrections policy

How to verify the version you can actually open

A provider page proves that a title exists and describes the supplier's intended rules. It does not prove that a casino accepts players in New Zealand, that the title is enabled for a particular account, or that the highest published RTP is the version in the lobby. Treat availability, operator eligibility and product configuration as three separate checks.

Start with identity, then configuration

Open the game only through the authenticated casino lobby. The information or help panel should identify Endorphina, the exact title and the active mathematical return. Compare the reel or grid layout, paylines or cluster rules, named features and symbol behaviour with the official product material. Similar artwork or a matching title is not enough when the help file is missing or inconsistent.

When the supplier publishes several RTP values, report all of them as configurations. Do not assume the highest option is deployed. RTP is a theoretical long-run measure across a very large number of rounds; it is not a refund rate for one player and cannot predict the next result. Volatility is different: it describes how unevenly results are distributed on the provider's scale.

Read stake controls as money, not interface decoration

Provider sheets often quote a reference range in euros. That range does not establish New Zealand-dollar support or the limits in a specific account. Before a paid round, identify the total amount that will leave the balance. If the interface separates denomination, coins and lines, verify the combined total. If Extra Bet is active, calculate its full cost before pressing spin.

Feature-buy prices are multiples of the current bet, not promised returns. A 100x purchase at a $1 stake costs $100; at a $2 stake it costs $200. Availability can vary by market and some mathematical configurations may not support the control. If the live help does not explain the price, delivered feature and active RTP, leave the option unused.

Keep simulation figures in their proper scope

A game sheet may publish a maximum result observed in a large simulation. That is not automatically the contractual maximum payout and never describes a likely session. Preserve the provider's wording, sample size and configuration. Check the live rules for a binding cap and the operator terms for any separate payout limit. Do not turn an extreme result into a promotional headline.

Audit a disputed round

If an animation freezes or a connection drops, do not repeat the wager immediately. Reopen the game through the authenticated lobby and inspect round history. Record the time, total stake, balance movement and round identifier. The result can be settled by the gaming system even when the device never displays the final animation. Send evidence through verified operator support; never disclose a password, recovery phrase or one-time code.

Read the paytable as a calculation document

The paytable should explain what creates a win, which symbols substitute, where special symbols can land and how multiple awards combine. For line games, confirm direction and active paylines. For cluster games, confirm adjacency, minimum group size and the order of collection. For respins, identify what remains locked, what resets the counter and what ends the feature. A graphic effect can illustrate those rules but cannot replace them.

Separate addition from multiplication. Several prize values may be added before a multiplier applies, while reel-specific multipliers can sometimes multiply together only when each reel participates in the same win. Reconstruct one low-stake result from game history. If the arithmetic cannot be matched to the help file, stop and ask the operator rather than guessing.

Do not confuse hit frequency with a profitable round

Provider sheets can publish hit frequency or category probabilities. A hit simply means a round returned a qualifying amount; it can be smaller than the stake. “Big”, “Mega” or “Epic” thresholds are provider reporting categories, not promises. They are useful for comparing mathematical versions only when definitions and samples are the same.

Random outcomes do not become due after a long gap. A feature that appeared repeatedly in a demo or marketing clip has no obligation to repeat in a funded session. Previous rounds do not create a debt from the next random result.

Confirm market and device behaviour independently

A title can exist in the supplier catalogue while an operator disables it for a territory, currency, device or bonus. Language localisation is not evidence of legal availability. Confirm the operator's identity, accepted countries and current lobby separately from the provider review.

On mobile, verify that balance, total bet, feature state and help remain visible without overlap. On desktop, check that browser zoom does not hide a purchase control or change the apparent denomination. Mathematical configuration should not change merely because the screen changes; if the help shows another RTP, treat it as a different deployment and record it.

Keep a compact evidence record

For any fact used in a review, save the title, provider, official URL, document date when available, access date and exact territorial scope. For a live session, add the operator domain, Game ID, RTP, currency and a non-sensitive screenshot of the help panel. This makes later corrections possible when a supplier updates a sheet or an operator changes configuration.

Missing information should remain missing. Do not estimate an RTP from results, convert a euro reference range into an operator's NZD limit, or treat another casino's configuration as evidence. A transparent “not confirmed” is more useful than a precise-looking number without the correct source.

Use limits that survive the feature design

Collection meters, expanding grids, sticky symbols and near misses can make a session feel unfinished. Unless the rules explicitly preserve progress, the visible state has no value after the round or feature ends. Set a money limit and time limit before launch, count feature buys immediately, and stop at the limit even when a meter appears close to an upgrade.

No random game is an income plan. Do not borrow, use essential funds or raise the stake to recover a loss. If play stops feeling recreational, use timeout, deposit-limit or self-exclusion tools and consult the site's responsible gambling guide.