Mr. Bells 40: map every bell before the encore

Mr. Bells 40 by Endorphina is listed with 40 fixed lines, 96.06% provider RTP, high volatility and a €0.40–€100 reference range. The checked page marks the game Approved and lists Wild, Scatter, Multiplier, Hold and Win and Pile. Bonus Pop is not listed.

The source labels Reels/Rows as 4×5, while its Bell Bonus description refers to a 5×4 grid of 20 positions. Those may be two ways of ordering the same dimensions, but a review should not silently reinterpret official wording. The live game help must identify reels, rows and the line map.

Published settings

Field	Provider record
Layout label	4×5; bonus text says 5×4
Paylines	40 fixed
RTP	96.06%
Volatility	High
Bet reference	€0.40–€100
Status	Approved
Bonus Pop	Not listed

This is a dated supplier record, not confirmation of an NZ operator listing or NZD limits. Save the live title, product ID, currency, total debit and help version before comparing a result.

Base game symbols and lines

The visual language uses fruit, bars, stars and bells. The watermelon is published at 2× base bet for five. That modest headline is useful because it shows why units matter: a symbol pay expressed in base bet cannot be compared directly with a bonus bell expressed in total bet.

The Flaming 7 is Wild. It can stack and substitutes except for Scatter and golden bell symbols. When several stacked Wilds appear, follow the 40-line map; do not assume an all-ways evaluation merely because adjacent reels look full.

Five star Scatters are listed at 1,000× base bet. Record whether a lower Scatter count pays and whether Scatters must be adjacent in the live table. A promotional star animation is not enough to reconstruct a win.

Bell Bonus trigger

Six or more golden bells start the Bell Bonus. The provider description treats the feature as a 20-position field. Map the transferred bells and their printed values before the first respin or hold action. Each new bell should have one cell, one value and one timestamp in the record.

The ordinary bell ladder includes 1×, 2×, 3×, 4×, 5×, 10×, 15×, 20× and 50× total bet. Keep these values separate from jackpot labels. If the live build uses fixed currency awards, record them exactly instead of converting them to multiples.

MIN, MID, MAX and ULTRA

The official page publishes MIN at 10× total bet, MID at 50×, MAX at 75× and ULTRA at 750×. These labels can appear alongside ordinary bells, but their settlement behaviour must be confirmed in help. Do not assume every label is added in the same way as a regular numeric bell.

Collecting all 20 bells makes every win in the feature x3, according to the provider. The order of operations matters: the help should say whether individual bell values, jackpot labels or the final aggregate are tripled. Do not choose the most generous interpretation from the animation.

The complete-grid condition is a published ceiling mechanism, not a prediction. A nearly full grid does not make the final position due and should not change a preset stopping point.

Pile and multiplier evidence

Pile is listed but the public page does not fully document its persistence or reset rule. Observe what is collected and capture the meter before and after a paid round. Never carry a Pile explanation across from another title just because the feature name matches.

“Multiplier” in the feature list can refer to the x3 full-grid rule or another presentation layer. Quote the live help before describing it more broadly. A feature tag is an index, not a complete contract.

Resolving the 4×5 / 5×4 conflict

Start by counting vertical reels and visible rows on the loaded base grid. Then compare the payline diagram. If there are five vertical reels with four positions each, record “5 reels × 4 rows” while retaining the source’s 4×5 label as an editorial note.

The Bell Bonus can still use 20 cells regardless of ordering. What matters is that a support report identifies cells unambiguously, for example reel three, row two. Include a screenshot with axes if the interface does not number positions.

Do not “fix” provider metadata in a citation. Report both statements, state which live display was observed and give the date. That preserves source integrity and helps readers distinguish a metadata convention from a mathematical discrepancy.

RTP and high volatility

The 96.06% value is a theoretical long-run setting on the official page. It does not guarantee a return, settle a dispute by itself or prove the configuration in every lobby. The in-game help and product ID are required for a deployment-specific statement.

High volatility describes the distribution design. It cannot tell a player when six bells or five Scatters will appear. A run without the Bell Bonus does not build entitlement to a trigger. Set a budget and session duration before starting.

Mobile and demo checklist

A demo can help locate the line map and feature help where it is legally and technically available. It does not verify New Zealand real-money availability and may not mirror an operator wallet.

On a phone, check that the total debit, all four or five dimensions, bell values and attempts counter remain legible. In landscape, make sure a notch or browser bar does not hide the outer reels. After an interruption, compare the same round ID before assuming the feature restarted.

New Zealand scope

The checked product page does not demonstrate that an identified New Zealand-facing operator offers Mr. Bells 40. The euro range cannot be represented as an NZD minimum or maximum. Currency conversion also does not establish a local stake configuration.

Check operator eligibility, game availability, live terms and responsible-gambling tools. Supplier approval and operator access are separate facts. If the title is absent, do not recommend location workarounds.

Worked Bell Bonus ledger

Suppose six bells trigger the feature. Record the paid-round debit once and sketch all 20 cells. Enter each starting bell, then number later states whenever a new bell arrives. Keep ordinary multiples in one column, jackpot labels in another and the remaining-attempt counter in a third.

If the twentieth cell fills, save the screen immediately before and after x3 is applied. Compare the displayed feature total with transaction history. Do not triple the summary manually if the credited value already includes the rule.

Base-game settlement check

For a Scatter or Wild dispute, capture the original grid, active line map and symbol table. Trace every claimed line from the required starting reel. Stacked Wilds can contribute to more than one line, but each line must still be enumerated rather than estimated visually.

Reconcile opening balance minus total debit plus the credited result. If another round or account adjustment occurred between those points, isolate it before filing a discrepancy.

Troubleshooting

If the counter freezes, stop play and capture the current grid, local time, game ID and history entry. Reconnect once. Repeated spins can make the disputed state harder to isolate.

Ask support whether the round completed server-side, what configuration was loaded and how the full-grid multiplier was applied. Remove account numbers and authentication details from screenshots. Never send a password or one-time code.

Common questions

Is the game 4×5 or 5×4?

The official metadata says 4×5 while bonus text says 5×4. Count the live grid and use its help screen, while preserving the source conflict.

Does a full grid pay 750× only?

The page lists ULTRA at 750× and separately says all 20 bells make every win x3. The live help must define their interaction.

Is five-star 1,000× a total-bet value?

The source describes it as base bet. Check that unit in the loaded paytable.

Is Bonus Pop available?

It is not listed on the checked page. Confirm the actual control set in the live build.

Final assessment

For comparison tables, record the live minimum total debit rather than dividing the published minimum by 40. An interface can define stake levels in ways that make that arithmetic wrong. The line count is fixed, but the relationship between coin value, line stake and total debit must still come from the loaded controls.

When the feature ends, retain both the pre-x3 aggregate and the final credit if the game exposes them. That pair is the clearest evidence for how the complete-grid rule operated. If only one amount is available, do not reverse-engineer the missing stage from promotional values.

Mr. Bells 40 rewards careful notation more than headline reading. The key tasks are resolving the dimension wording, separating base-bet symbol pays from total-bet bells and documenting the full-grid x3 order.

The official page supplies a strong starting record, but live help must settle layout and multiplier interpretation. Stop at the planned boundary, even when the bell field is almost complete.

Official and related sources

• Mr. Bells 40 official page
• Endorphina catalogue guide
• Review methodology
• Responsible gambling
• 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.