Book of Ganesha: expanding symbols and the Sacred Hold Bonus

Book of Ganesha by Endorphina is listed as a 5×3, ten-line game with 96.03% provider RTP and high volatility. The checked studio page gives a €0.10–€45 reference range, marks the title Approved and lists Risk, Bonus Pop, Scatter, Hold and Win and Free Games.

The theme does not replace the rules. This review tracks the dual-purpose Book, an expanding-symbol Free Games route and a separate gold-coin Hold feature. It does not claim that a particular New Zealand operator carries the game or that the euro range applies to an NZD account.

Published configuration

Field	Provider record
Grid	5×3
Paylines	10 fixed
RTP	96.03%
Volatility	High
Bet reference	€0.10–€45
Status	Approved
Bonus Pop	Listed; jurisdiction-dependent

Approval on a supplier page is not the same as operator authorisation. Record the exact title, product ID, operator domain and help version. If the loaded percentage or range differs, the in-game screen governs claims about that deployment.

The Book as Wild and Scatter

The Book performs two jobs: it is Wild and Scatter. As Wild it substitutes according to the live paytable; as Scatter it can trigger the free-round route. The public page says five Books pay 200× base bet. Before calculating that amount, check how the build defines base bet versus total paid stake.

Three or more Books trigger ten Free Games with an expanding symbol. A Book can therefore contribute to a pay, a trigger or both. Transaction history may bundle these outcomes, so record the trigger grid and the eventual feature credit rather than summing headline numbers without context.

Free Games and the selected symbol

The expanding symbol route needs a precise sequence. Capture the symbol-selection screen, its position in the paytable and the starting spin count. During each free round, note whether the selected symbol expands before or after ordinary line evaluation and whether enough matching symbols are required to activate expansion.

The official page establishes ten starting spins but does not settle every edge case. Check retriggers, coinciding Books, multiple line wins and any cap in the live help. Number the free rounds and keep the summary under the original paid trigger.

An expanding low symbol can create many line combinations but may still settle below a rarer high symbol. Visual coverage is not the same as monetary value. Use the paytable and active ten-line map.

Sacred Hold Bonus

Six or more gold coins trigger the Sacred Hold Bonus. Qualifying coins transfer to the feature grid and display values. The provider publishes ordinary coin values up to 20× total bet and four fixed feature labels: MIN at 25×, MID at 50×, MAX at 100× and ULTRA at 1,000× when all 15 positions are filled.

Map the initial six or more coins before the first respin. For each subsequent state, note newly occupied cells and the attempts counter. A coin that replays an animation without changing the grid should not be entered twice.

The 15-cell Ultra condition is a rule threshold, not a likelihood statement. Confirm whether the live build uses the same labels and whether jackpots are stake multiples or fixed currency values. Never convert a fixed value with an invented exchange rate.

Ganesha symbol and paytable context

The Ganesha character is the leading regular symbol, with the public table giving 500× base bet for five. This relatively large base-bet multiple can be misunderstood when a player compares it with coin values expressed in total bet. Keep the units visible in separate columns.

Write “base-bet multiple” beside regular symbol pays and “total-bet multiple” beside feature coins. If live help uses a different unit, quote that definition. Do not normalise unlike values merely to make the table look simpler.

Bonus Pop and Risk controls

Bonus Pop is listed, but availability and pricing may vary by jurisdiction and operator configuration. A purchase label is not part of the mathematical evidence unless its price, starting state and RTP treatment are disclosed in the same live help. If absent, mark it unavailable.

Risk is a decision after a win, not a modification of the original spin. Save the original settled amount before using it. If the gamble loses, history should still show how the first win became the amount placed at risk.

Understanding 96.03% and high volatility

RTP is a theoretical long-run property. The published 96.03% does not guarantee that percentage for one session and does not prove the setting used by every integration. A reliable comparison places the provider value beside the live-help value and date.

High volatility means results can be uneven. It does not indicate that a Book, coin or Ultra award becomes due after a particular number of rounds. Set both a money limit and a time limit independently of visible collection progress.

Mobile and demonstration checks

Where a provider demo is accessible, it can help locate help screens and practise recording states. It does not prove real-money availability in New Zealand or identical wallet settings. Age, location and site restrictions still apply.

On a phone, verify that the total debit, ten-line map, selected expanding symbol and Hold counter remain readable. Test portrait and landscape. If the app is backgrounded during a feature, capture the round ID before and after return so a resumed animation is not mistaken for a second result.

New Zealand scope

The product page does not by itself verify a New Zealand operator listing. Avoid phrases such as “available in NZ” unless an identified operator and account state provide current evidence. Currency, minimum stake and Bonus Pop access can differ by deployment.

Supplier approval, operator permission and player eligibility are separate. Check all three layers. If one cannot be documented, report it as unavailable rather than filling the gap with a general casino claim.

Worked Free Games audit

Suppose three Books trigger the feature. Record the debit and trigger pay, then save the selected symbol. Number spins one through ten. For every expansion, note the pre-expansion grid, completed grid and line total. Add retriggers only when the help confirms their rule and the counter changes.

At the summary, compare the feature total with transaction history. Do not add the displayed running total again if the same amount is already the final credit. Reconcile opening balance minus one paid-round debit plus one final settlement against closing balance.

Worked Sacred Hold audit

For a six-coin trigger, sketch the 5×3 grid and enter the printed value in each occupied cell. Record the attempts counter after every new coin. Separate ordinary coin values from MIN, MID, MAX and ULTRA labels; those are not interchangeable categories.

If all positions fill, verify that the 1,000× rule is applied to total bet as the provider states. If the live summary differs, stop and save the help text, feature grid and transaction ID before contacting support.

Troubleshooting and support evidence

If the game interrupts, stop further play. Capture the selected symbol or Hold grid, remaining count, local time and product ID. Reconnect once and examine history. Screenshots should omit account names, payment details and authentication codes.

Ask support for the transaction ID, loaded RTP and settlement explanation. A useful question identifies the disputed state: Book trigger, symbol expansion, coin transfer, counter reset or final credit. “The bonus looked wrong” is too vague for a reproducible review.

Common questions

Are ten Free Games always awarded?

The provider page states ten for three or more Books. Confirm retriggers and any deployment-specific wording in live help.

Is five-Book 200× a total-bet value?

The public page describes it as base bet. Check the build’s definition before converting it to currency.

Does six coins guarantee a jackpot?

No. Six or more trigger the Sacred Hold Bonus; the feature rules determine subsequent values and labels.

Is the 1,000× Ultra an expected return?

No. It is the published full-grid award, not a forecast.

Final assessment

A final comparison should keep three documents together: the selected-symbol screen for Free Games, the opening coin grid for Sacred Hold and the final transaction entry. None can replace the others. The first establishes the rule state, the second establishes transferred value, and the third establishes what the wallet actually received.

If the interface localises currency or decimal separators, copy the displayed value before converting it for personal notes. A decimal-format error can be larger than the difference being disputed. Support evidence should preserve the original display and state the account currency explicitly.

Book of Ganesha is easiest to verify when its two bonus systems remain separate. Books govern the expanding-symbol sequence; gold coins govern a 15-cell Hold record. Combining their values or units creates avoidable errors.

Use the provider page as a dated reference, the live help as deployment evidence and transaction history as settlement evidence. Stop at the planned limit regardless of collection progress or feature imagery.

Official and related sources

• Book of Ganesha 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.