NZ-NI-0398 · supplier source record
Thunder Crown: lightning tokens and five charged columns
Token discharges uncover symbols and may open a Hold feature with columns of different heights. The unusual grid deserves a cell-by-cell record.
Supplier sources below. Operator eligibility needs a separate check.

Thunder Crown by Endorphina is documented on the checked studio page as a 5×5 game with 50 fixed, 96.05% RTP and medium volatility. The published reference stake is €0.50–€100; the page is marked Approved. Listed features are Wild, Risk Game, In-Game Free Spins, Scatter and Multiplier.
Those Thunder Crown details describe the supplier page checked on 7 October 2026. They do not confirm a New Zealand operator listing, an NZD range or the configuration in a particular account. This review therefore separates provider evidence from values that must be read in the exact live build.
Published settings
| Field | Provider record |
|---|---|
| Grid | 5×5 |
| Evaluation | 50 fixed |
| RTP | 96.05% |
| Volatility | Medium |
| Bet reference | €0.50–€100 |
| Status | Approved |
Approval is supplier metadata, not operator permission. Save the full title, product ID, operator domain, currency and help version. If the live screen differs, use its values for deployment-specific claims and retain the provider page as a dated comparison.
How the main feature works
Three or more Scatter Stars trigger Free Games, with at least one Wild guaranteed on each free spin; the feature can retrigger. Tokens appear in the base game and Free Games, discharge into the crown, disappear and uncover a symbol that may complete a win. A discharge may randomly open Thunder Hold. Its five columns have different heights, Thunder Spheres carry 1× to 30× values, and completing a column awards a jackpot from 50× to 1,000× total bet. Multiple completed columns can each pay.
The feature description is not a promise of frequency. Record the paid trigger once, place every bonus state beneath that parent transaction and use wallet history for the final credit. Do not add a feature summary twice when it already contains the component awards.
Symbols and paytable evidence
The Crown is Wild and substitutes except for Scatter and Token. Wilds appear on reels two to four and expand vertically. Five sevens pay 200× base bet.
Base bet, line bet and total bet are not interchangeable. Copy the definition shown in help before converting a multiplier to currency. A promotional image can identify a theme, but only the paytable establishes a symbol value and its qualifying pattern.
A feature-specific audit
A rectangular sketch is inadequate for the Hold feature because column heights differ. Draw each column separately, mark its capacity and record the jackpot attached to a completed column.
Capture the state before an animation clears. Use sequence numbers, not memory: initial grid, trigger, every counter change, final summary and transaction entry. If a value remains unexplained, mark it unresolved instead of selecting the most generous interpretation.
RTP and volatility
The published 96.05% RTP for Thunder Crown is a theoretical long-run setting. It cannot forecast one session, guarantee a return or prove that every operator loads the same certified option. A short sample is too noisy to validate it. Put the provider value beside the live-help value and date.
Medium volatility describes distribution, not a timetable. A feature does not become due after a quiet sequence. Set money and time limits before opening the game, and do not extend them because a meter, token or animation appears close to completion.
Mobile and demo verification
The provider may offer a demonstration subject to age, location and site policy. Demo access does not prove real-money availability in New Zealand, and its wallet or configuration may differ from an operator integration.
On mobile, test portrait and landscape. The total debit, outer reels, counters, multipliers and help control should remain readable without horizontal clipping. If the browser is backgrounded, compare round identifiers before treating a resumed animation as a new award.
New Zealand availability boundary
The Endorphina product page does not itself verify that Thunder Crown is available through an identified New Zealand-facing operator. The euro range is not an NZD promise. Check operator terms, account location, currency, product ID and responsible-gambling controls.
Supplier status and operator access are separate evidence layers. If the title is absent, record availability as unconfirmed and do not recommend technical or location workarounds. A current account screen is stronger evidence than a third-party catalogue card.
Worked settlement record
Begin with opening balance and one total debit. Save the triggering grid and active evaluation rule. Number all feature stages in chronological order, including any retrigger, collector update, cascade or sticky state. At the end, compare the final feature total with transaction history.
Opening balance minus the debit plus the credited result should reconcile to closing balance when no other activity intervenes. If it does not, preserve local time, time zone, game ID, help version and screenshots with personal data removed.
Troubleshooting
If the game interrupts, stop placing rounds. Capture the visible grid, counter, last accepted event and transaction reference, then reconnect once. Repeated refreshes or additional spins can obscure the disputed state.
Ask support to identify the server-side round status, loaded RTP and settlement rule. State whether the question concerns the trigger, counter, symbol evaluation or final credit. Never send a password, payment credentials or authentication code.
Comparison checklist
A useful Thunder Crown comparison asks whether the live minimum debit is affordable within a preset entertainment budget, whether rules remain legible on the intended device, whether history exposes a stable round ID and whether optional controls clearly state their price. Headline maximums alone answer none of these questions.
Keep units attached to every number. A jackpot expressed in total bet cannot be compared directly with a regular symbol expressed in base bet. Fixed currency values should remain in their displayed currency unless a documented conversion is required.
Evidence before, during and after the round
Before opening Thunder Crown, create a compact configuration record: displayed title, product identifier, 5×5 grid, 50 fixed evaluation, 96.05% help value, account currency and total stake. Save the relevant help page rather than a lobby tile. A lobby image can survive a software revision, whereas the rules file normally identifies the build actually loaded.
During play, ignore decorative movement and record only rule-changing events: a qualifying symbol, accepted token, changing counter, locked position, multiplier activation or extra award. A rectangular sketch is inadequate for the Hold feature because column heights differ. Draw each column separately, mark its capacity and record the jackpot attached to a completed column. This focus produces a shorter but stronger record and lets another reader reproduce the calculation.
After settlement, save the transaction line before another round. Compare its identifier with the trigger. If Thunder Crown presents a running total and a final total, determine whether the latter already includes the former. Reliable arithmetic begins with balances and one debit, not by adding every number that flashed on screen.
Reading the source critically
Endorphina is the primary public source here, but its product page is still a summary. Feature badges such as Wild, Risk Game, In-Game Free Spins, Scatter and Multiplier identify areas to inspect; they do not replace complete help. Marketing copy can omit counter resets, award order, cap behaviour and configuration variants. This guide uses only numeric details exposed by the checked source and leaves unresolved deployment questions to the loaded rules.
The €0.50–€100 range is easy to misuse. It is denominated in euros and may describe a reference configuration. It cannot be converted into an asserted NZD minimum because a lobby may expose different steps or rounding. Quote the local control only after observing it in an eligible account.
Session planning for this mechanic
Choose a fixed loss limit and duration before using Thunder Crown. Divide the money boundary by the confirmed total debit to understand the maximum possible number of paid rounds, while allowing an earlier stop. Optional Risk or purchase controls are not free extensions; their cost or exposure belongs inside the same limit.
Do not set a Thunder Crown target based on recovering earlier losses, reaching a visible meter or seeing a named jackpot. Feature art is designed to hold attention, not measure proximity to a random result. At the boundary, save the completed transaction and leave without placing a test round.
Common questions
Is 96.05% guaranteed in every lobby?
No. It is the checked provider-page value. The exact live help is required for a deployment-specific statement.
Does the published stake range apply in NZD?
No. €0.50–€100 is a euro reference. The account interface must confirm local currency and limits.
Can a demo prove real-money availability?
No. It can explain controls and rules, but not operator access, eligibility or an identical configuration.
Should a player continue because a feature looks close?
No. Visual progress does not make an outcome due. Stop at the preset budget and time boundary.
Final assessment
Thunder Crown should be reviewed as an identified software build, not a lobby thumbnail. The official page establishes a useful baseline; live help supplies the deployed rules; transaction history supplies settlement evidence.
The practical method is simple: label units, preserve the parent round, record each state once and leave unresolved details unresolved. Presentation never overrides the stopping plan.
Official and related sources
- Thunder Crown 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.
Primary source and correction path
This guide separates documented product information from market availability. Check the official source and the game help inside the exact version offered before making a decision.
