Take The Kingdom seven-round rules and evidence

Take The Kingdom is listed by Betsoft as live from 9 December 2021. The official page gives five reels, 100 paylines, 96.53% RTP, medium volatility and a 37.55% hit rate. The base game operates in seven-spin increments while fireballs count down and later convert their positions to Wilds.

Three scatters award 12 free spins. Before the feature, the game selects 6, 9 or 12 Wilds; that number remains constant but the Wild positions move on every free spin. A Buy Feature route is also documented.

Verified specification

Field	Official value	Deployment check
Listed live date	9 December 2021	Build revision
Reels	5	Visible grid
Paylines	100	Route and direction
RTP	96.53%	Active profile
Volatility	Medium	Studio label
Hit rate	37.55%	Not profit frequency
Base cycle	7 spins	Boundary and reset
Free spins	12 from 3 scatters	Retrigger rules

Seven-spin base cycle

The title is played in seven-spin increments. Fireball bombs occupy positions and count down across the sequence, then explode and convert all recorded fireball positions into Wilds.

Before the first spin, record the cycle counter. For each step, save new fireballs, their positions and countdown values. At the seventh settlement, compare the accumulated position set with the Wild conversion.

Do not treat the cycle as seven free spins. Each base step may be a paid spin; confirm the displayed total stake and wallet deduction on every one. A visual progression is not stored money and should not override a stop limit.

Fireball position ledger

Draw the reel grid and assign coordinates. When a fireball appears, record its coordinate and counter. If another fireball lands on the same position, Help should define whether it replaces, refreshes or stacks.

At explosion, circle every converted position and trace resulting wins through the 100-line breakdown. The conversion order matters: awards should be calculated from the post-conversion grid if Help says Wilds appear before evaluation.

If a session closes mid-cycle, save the counter and reopen without wagering. Record whether the sequence persists. Do not place another spin simply to discover whether state was stored.

Free spins and selected Wild count

Three scatter symbols trigger 12 free spins. Before the round begins, the game selects 6, 9 or 12 Wilds. The chosen quantity remains the same for the entire feature.

Record the selection screen, opening counter and initial Wild coordinates. On each free spin, verify that the number remains fixed while positions change. A moved Wild should not be counted as an additional Wild.

The public page does not state the probabilities for selecting 6, 9 or 12. It also does not publish retrigger behaviour. Leave both unavailable unless current Help resolves them.

Moving-Wild map

Use one diagram per free spin. Number the Wilds consistently only if the interface identifies individual objects; otherwise record the set of occupied coordinates. Compare the count before and after settlement.

List every winning line after positions are final. With 100 paylines, history is more reliable than visual estimation. Preserve any scatter award separately from feature wins.

At the end of spin 12, confirm that all moving Wild state clears before the next paid cycle. A replayed animation after reconnect should be checked against server history.

Raid the Dragon’s Hoard purchase

Betsoft describes a Buy Feature button providing access to free spins. The accessible page does not publish price, return variant, territorial availability or which Wild count is guaranteed.

If enabled, capture the confirmation screen before purchase. Record cost, selected Wild count, RTP and final settlement. Feature purchase is a wager and must not be described as an operator bonus.

Do not claim that New Zealand accounts can use the control. A provider-global description and a local operator deployment are different evidence scopes.

RTP, hit rate and limits

The official return is 96.53% and hit rate 37.55%. A hit may return less than the stake, while the RTP is meaningful only across the mathematical long run.

The public page does not state the stake range, maximum win or fireball probability. Third-party estimates are excluded. Current Help and operator terms are required for limits.

If Buy Feature uses another RTP profile, show it separately. Never merge base RTP, purchase price and maximum from different deployments.

Mobile and continuity audit

At 390-pixel width, the cycle counter, each fireball timer, total stake and full reel grid must remain visible. Moving Wilds should have clear coordinate changes rather than motion alone.

Test orientation before starting a sequence. Reopen the title after a non-wagering interruption and verify persistence against history.

Reduced-motion mode must retain counters and final Wild locations. Commercial overlays should not hide the seventh-spin conversion or feature-purchase confirmation.

Demo and territorial boundary

Betsoft links an official demo. Sponsored links here are not that demo. The provider catalogue does not prove availability in New Zealand or at 22Bet.

Check operator access, territorial conditions and live Help independently. Describe only the tested deployment and date.

Reader fit

Take The Kingdom may suit readers who like predictable feature timing and state tracking. The seven-step sequence is transparent only when every paid deduction and fireball counter is recorded.

It may not suit anyone tempted to continue solely because the seventh spin is near. Progress through a cycle does not change the need for a fixed budget and stopping rule.

Evidence checklist

Complete seven-step cycle sheet

Create seven numbered rows before the cycle starts. Each row should contain opening cycle counter, total stake, new fireball coordinates, existing fireball counters, ordinary line wins, closing balance and round ID. This establishes whether every step is independently paid and makes an interrupted cycle recoverable.

Use a consistent coordinate system such as reel one through five and top-to-bottom row letters. When a fireball lands, place its starting counter beside the coordinate. On later spins, copy the displayed value rather than subtracting mentally; the client may update counters before or after settlement.

At the seventh step, freeze the screen before conversion if possible, then save the Wild-filled result. Compare the set of accumulated fireball coordinates with the set converted to Wilds. If one position is missing or an additional position appears, check Help and history before describing the rule.

Trace the final Wild grid through the 100-line breakdown. Keep ordinary symbol awards from earlier steps separate from the seventh-spin conversion award. The entire sequence is a progression of paid rounds, not one wager, unless the deployed Help explicitly says otherwise.

For free spins, start a different twelve-row sheet. Write the selected quantity—6, 9 or 12—at the top and count occupied Wild coordinates on every spin. Their positions should move while their number remains fixed. If two Wilds overlap visually or a position is hidden by animation, use the static result history.

Record any retrigger or special event in its own column rather than changing the selected Wild count. At feature end, compare the sum of all twelve settlements with the wallet credit and confirm the next base-game counter state.

This pair of sheets distinguishes three ideas that are easy to blur: accumulating fireball locations, one final base conversion and a fixed quantity of moving feature Wilds. None of them represents recoverable value before server settlement.

For a correction audit, compare cycle persistence after a normal page refresh, a short disconnect and a full sign-out without placing a new wager. Record only what the interface and history reveal. If the counter resets visually while server history retains the sequence, contact support before publishing a conclusion.

The same caution applies to feature purchase. A confirmation panel may show a price but omit a separate RTP; absence of a displayed variant is not proof that the mathematics are identical. Mark the profile unavailable until primary evidence resolves it.

Retain the dated confirmation screen for later comparison and correction review.

Keep the matching round identifier beside that capture.

1. Match title and Betsoft provider.
2. Confirm 96.53% RTP and 100 lines.
3. Record every paid deduction in the seven-spin cycle.
4. Map fireball positions and counters.
5. Save the seventh-spin Wild conversion.
6. Record 6, 9 or 12 feature Wilds.
7. Verify 12-spin count and moving coordinates.
8. Document Buy Feature only if enabled.

FAQ

What RTP does Betsoft publish?

96.53%.

How long is the base cycle?

Seven spins, during which fireballs count down before converting to Wilds.

What triggers free spins?

Three scatters award 12 free spins.

How many moving Wilds appear?

The game selects 6, 9 or 12 before the feature, and the chosen count remains constant.

Is feature purchase guaranteed locally?

No. Territory and operator deployment must be checked.

Is NZ availability proven?

No.

Sources

• Betsoft, Take The Kingdom, official product page, checked 9 October 2026.
• Betsoft official games catalogue, checked 9 October 2026.

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 Betsoft, 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.