Fruletta and Dice: Wheel of Fortune rounds compared

Fruletta and Fruletta Dice are separate Endorphina catalogue titles with the same published configuration: five reels, three rows, nine paylines, 96.04% RTP, low volatility and a €0.09–€180 reference stake range. Three, four or five Bonus symbols award one, two or three Wheel of Fortune rounds respectively.

One canonical page covers the shared search task, while every observation remains tied to the exact edition loaded. Neither official listing proves access through a particular New Zealand account.

Side-by-side settings

Field	Fruletta	Fruletta Dice
Grid	5×3	5×3
Paylines	9	9
Provider RTP	96.04%	96.04%
Volatility	Low	Low
Bet reference	€0.09–€180	€0.09–€180
Wheel rounds	Up to 3	Up to 3

The matching headline settings do not make the paytable art interchangeable. Save the title screen, version and help for whichever edition is reviewed.

Nine-line evaluation

Ordinary wins are added across the nine paylines. Record the current line diagram, total bet and symbol count. The provider pages do not justify guessing a path from neighbouring artwork alone.

Bonus symbols count anywhere and use their count to determine Wheel rounds. They are not required to form a conventional left-to-right line. Keep the Bonus count separate from ordinary line settlement.

If several ordinary lines win in the same spin, reconcile them against the combined history entry. The Wheel entry is a state change and should not be treated as another line award unless the active paytable separately pays Bonus symbols.

Wild exclusions

In Fruletta, the golden bell Wild substitutes for ordinary symbols except the Wheel Bonus symbol and the seven. Five Wilds are published at 222× base bet. The seven remains the protected top-paying symbol.

In Fruletta Dice, the Wild substitutes for all ordinary symbols except Bonus and the main red die. The official summary calls five Wilds “around 222×” base bet. Because that wording is approximate, the live Dice paytable must supply the exact configured value.

Record which edition is loaded before describing a protected symbol. A seven belongs to the fruit version’s explanation; a red die belongs to the Dice version.

One, two or three Wheel rounds

Three Bonus symbols trigger one Wheel round, four trigger two rounds and five trigger three rounds. Write down the trigger count and opening round balance before the wheel begins. This avoids calling a five-symbol trigger one long spin or assuming every entry receives three rounds.

The Dice page states that the Wheel offers multipliers up to 100× and spins until it lands on Collect. The public fruit page confirms the round ladder but its summary does not publish the same precise Wheel sequence. Use current help to verify whether both editions share the same stop logic and multiplier table.

For each Wheel round, record every displayed step, any accumulated value, the Collect result and the settled credit. Animation positions are not separate awards unless the rules say they accumulate.

Wheel ledger

Start with title, version, RTP, total bet, Bonus count and number of awarded rounds. Create one row for each Wheel round with starting state, intermediate multiplier markers, Collect point, round value and running feature total.

If the wheel passes a 100× segment without stopping, that segment is not automatically won. The active result is determined by the mechanism described in help and the final Collect settlement. A visual near miss has no separate value.

After all awarded rounds finish, compare their sum with the feature summary and transaction history. If the summary is inclusive, do not add it again. Preserve round IDs or timestamps for support.

Fruit paytable examples

The fruit edition lists five sevens at 556× base bet, five golden-bell Wilds at 222× and five watermelons at 56×. These are examples from the supplier page, not a complete paytable.

Confirm whether “base bet” equals one line unit or another configured value before converting multipliers to cash. Nine-line total stake can differ from the basis shown beside symbol prizes.

The Wild excludes the seven, so a bell should not be assumed to complete a five-seven line. Trace the actual symbol combination and substitution rule before calculating it.

Dice paytable evidence

The Dice edition describes the red die as the highest-paying symbol and says five pay “around 555×” base bet. It similarly describes five Wilds as “around 222×”. The approximate language is a reason to quote the loaded paytable, not to round the fruit values and call them identical.

Build a Dice-specific record with exact symbol face, count, multiplier and wager basis. Do not map a particular coloured die to a fruit simply because its place on the reel strip looks comparable.

The structural comparison is valid at grid, line, RTP and feature level. Exact Dice prize claims require its own help evidence.

Bonus Pop and Classic Risk

Both official pages list Bonus Pop, with availability dependent on casino and jurisdiction. Record any displayed purchase or access cost, the feature obtained and relevant RTP note. Bonus Pop is not a free Wheel entry.

The Dice page also lists Classic Risk, and provider text says eligible wins can be doubled up to 10 times. The fruit page’s feature icons emphasise Roulette and Bonus Pop, so do not assert Risk in a particular fruit deployment without checking its interface.

Risk decisions occur after a settled win and should be logged separately from Wheel rounds. A possible doubling path is not part of the Wheel’s published maximum.

RTP, mobile and access

The 96.04% RTP is the supplier’s long-run setting for both pages. It does not predict a Bonus count, Wheel stop or profitable session. Low volatility is a category, not a guarantee against losses.

On mobile, check that all Bonus symbols, the awarded-round counter and wheel pointer remain visible. Open help in both orientations and verify history access before play.

The euro stake range is not an NZD limit. Record the actual currency, total bet and operator domain. Catalogue presence does not prove New Zealand access.

Worked three-round example

Assume five Bonus symbols appear in Fruletta Dice. The published ladder awards three Wheel rounds. Create three ledger rows before the first wheel starts. During round one, record each displayed step but assign value only when the wheel reaches its rule-defined Collect result. Repeat for rounds two and three, then compare their combined value with the feature summary.

If a 100× segment is visible but the wheel does not settle there, it is not automatically credited. “Up to 100×” describes the published Dice ceiling, not the result of each entry. The history entry determines the actual award.

Now compare a four-Bonus trigger in the fruit version. It should open two rounds, not inherit the Dice example’s three. Use the fruit help to identify its wheel table and settlement. This illustrates why shared feature structure does not justify copying one edition’s exact outcomes into the other.

Version-control checklist

Store two source records: one for Fruletta and one for Fruletta Dice. Each needs the official product URL, access date, loaded version, RTP, paytable screenshot and operator observation. When a provider page changes, update only that edition’s source record until the other is rechecked.

For symbol values, label published exact figures and approximate wording separately. The fruit page gives 556×, 222× and 56× examples, while the Dice summary uses “around” for 555× and 222×. A table should preserve those qualifiers rather than normalising them into false precision.

For Wheel behaviour, distinguish three claims: how many rounds the trigger awards, how a round proceeds, and which multiplier settles. The shared trigger ladder is documented for both. The Dice page explicitly describes spinning until Collect and a 100× ceiling. The active fruit help should confirm whether its implementation uses the same wording.

Preparing a precise support question

Attach the trigger grid, number of awarded rounds, wheel state before Collect, final feature summary and transaction history. Include title and edition in the subject line. A question about missing Wheel value should identify the exact round and stop position rather than cite another edition’s promotional page.

If the disagreement is about Wild substitution, provide the payline and protected top symbol. The golden bell cannot substitute for the fruit seven; the Dice Wild cannot substitute for the main red die. This makes the expected calculation reproducible.

Redact balance and account details before publishing evidence. The technical fields needed for verification are game version, round ID, timestamp, wager unit and state transition.

Common interpretation errors

• Treating Fruletta and Fruletta Dice as one executable version.
• Giving three Wheel rounds for every qualifying trigger.
• Allowing the Wild to substitute for seven or red die.
• Calling every wheel segment passed an award.
• Publishing approximate Dice values as exact multipliers.
• Transferring fruit symbol values directly to coloured dice.
• Calling Bonus Pop free or universally available.
• Presenting the supplier catalogue as proof of local access.

Final assessment

Fruletta’s central audit is a count-and-settlement exercise: count three to five Bonus symbols, award one to three Wheel rounds, record each Collect result and keep fruit and Dice paytables labelled separately.

The official pages support the shared configuration and round ladder. Current help must resolve exact Dice multipliers, Wheel sequence, optional controls, wager basis and operator availability.

Official and related sources

• Fruletta official product page
• Fruletta Dice 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.