Tiger’s Claw rules and 720-way evidence

Tiger’s Claw is listed by Betsoft as live from 22 March 2018. The official page gives 95.14% RTP, high volatility, a 36.28% hit rate, 720 ways and a 3-4-5-4-3 reel layout. Free spins come from claw symbols across the reels, while three or more Shaman symbols pay as scatters.

The source contains one material inconsistency: its overview says up to 98 free spins can be awarded in one spin, while the detailed feature block says up to 96. Both cannot be treated as one verified value. This review keeps the conflict visible and directs readers to the deployed Help for the controlling rule.

Official record and evidence status

Field	Published value	Status
Listed live date	22 March 2018	Verified at studio level
Reel heights	3-4-5-4-3	Verified
Ways	720	Verified
RTP	95.14%	Verify active build
Volatility	High	Studio classification
Hit rate	36.28%	Long-run statistic
Initial free-spin ceiling	98 in overview; 96 in feature text	Uncertain
Total feature ceiling	240 free spins	Published
Shaman scatter	2× to 50× total wager	Published

How the 720 ways are formed

The centre reel is tallest, with five positions; adjacent reels have four and the outer reels have three. “All Ways Pays” normally requires matching symbols on adjacent reels beginning from an eligible edge, but the accessible page does not spell out direction or Wild behaviour.

To verify a win, number each visible position by reel and row. Highlight every occurrence of the paying symbol on consecutive reels, then calculate the number of valid combinations. Do not treat 720 as 720 drawn paylines; it is the total route count produced by the 3-4-5-4-3 geometry.

If Help says wins pay both ways, document the two origins separately. If it specifies left-to-right only, do not infer a reverse route from the diamond shape. The full paytable controls the symbol value after route count is known.

Claw trigger and the 96-versus-98 conflict

Betsoft’s detailed feature text says five Free Spin symbols trigger the mode and that one win can award up to 96 free spins. The overview instead says combinations of five Claws can add spins up to 98 in a single spin. This may be a copy error, revision difference or distinction between calculation stages, but the public page does not explain it.

The defensible approach is to quote both and mark the initial ceiling uncertain. Open the deployed Help, capture the claw award table and identify the exact build. If it says 96, use 96 for that deployment; if it says 98, preserve the screenshot and date. Do not average the figures or silently choose the larger one.

The page agrees that additional free spins can be won during the feature and publishes a total ceiling of 240. A ceiling does not describe frequency. High volatility and a large possible counter should not be converted into an expectation of a long feature.

Retriggers during free spins

Golden Tiger’s Claw symbols can add spins during the feature. Record the opening counter, number of claw symbols in the retriggering result, awarded increment and new counter. This establishes whether the counter adds before or after one spin is consumed.

If several five-claw combinations appear on the same screen, Help should show how they are counted. The overview implies more combinations add more spins, but it does not publish a complete mapping. Route arithmetic for normal symbol wins should not be reused automatically for free-spin awards.

The total 240 limit is best tested as a cap on the displayed counter or accumulated awards, depending on Help wording. Never suggest the counter will reach that value; it is only the maximum Betsoft publishes.

Shaman scatter awards

Three or more Shaman symbols scattered anywhere award between 2× and 50× total wager. Because this is explicitly tied to total wager, it should not be recalculated using line stake. Record the number of Shaman symbols and the paytable multiplier.

Check whether Shaman awards coexist with a normal ways win or a claw trigger. If multiple events settle on one screen, history may itemise them or show one combined credit. Preserve the component labels so no award is counted twice.

The public source does not list the precise multiplier for each possible Shaman count. That mapping remains a live-paytable fact. The 2×–50× range is verified, but assigning intermediate values would be invention.

Worked grid audit

Draw five vertical columns with heights 3, 4, 5, 4 and 3. On a settled spin, write each symbol into its exact cell. For a normal award, trace adjacent-reel combinations and multiply the number of valid occurrences by the paytable value.

On a claw screen, mark each claw separately and record the awarded spins shown by history. On a Shaman screen, ignore adjacency and count the scattered symbols. This distinction is essential: one visual grid contains three different evaluation systems.

If the result triggers free spins and pays Shamans simultaneously, use one round ID with separate lines for the scatter award and state transition. The following free spins should show no new paid stake.

RTP, hit rate and risk

The 95.14% RTP and 36.28% hit rate are studio-level values. A hit can return less than the amount staked, and neither percentage predicts whether the next spin wins. High volatility indicates uneven outcomes across the model.

No stake range or maximum-win multiplier is exposed in the accessible official text. Values from third-party reviews conflict, so they are excluded. Use the exact Help screen and operator rules for a current cap.

If live Help shows another RTP, preserve both records and label their scope. A deployment-specific value outranks an old aggregator table for the game actually loaded.

Mobile evidence routine

The unusual diamond grid is easy to crop on a narrow screen. Confirm that all three positions on the outer reels, all five on the centre reel and the free-spin counter remain visible without horizontal scrolling.

At 390-pixel width, check total stake, balance, Help and history access. Rotate before beginning a feature and confirm that the claw counter survives orientation change. Promotional overlays must not hide the rightmost reel.

The claw and Shaman symbols need more than colour to distinguish them. If animation is fast, history should provide a static result. Record any accessibility limitation rather than relying on a paused video frame.

Demo and territorial boundary

Betsoft links an official demo, but the sponsored routes in this guide are not that demo. The provider page proves that the studio documents the game; it does not prove New Zealand availability or a listing at 22Bet.

An authenticated account check should match title, provider, RTP and game ID. If a local catalogue does not show Tiger’s Claw, state only that it was unavailable in that tested account on that date.

Who may prefer Tiger’s Claw

This format may appeal to readers who like ways-based grids and a feature with a visible spin counter. It requires more careful verification than a fixed-line game because normal ways, claw awards and Shaman scatters use different logic.

It may not suit readers seeking low-variance pacing or a precisely documented maximum. The official source itself conflicts on the initial free-spin ceiling, which makes checking live Help especially important.

Correction note for the provider conflict

An editor revisiting this page should not remove the 96-versus-98 warning merely because one live deployment displays one value. First archive the Help screenshot, game ID and date, then check whether Betsoft has corrected either section of its public page. The studio page and the deployed build are separate evidence objects.

If the provider later aligns both statements, update the verified table and modified date while retaining a short correction note. That creates an auditable history instead of making the earlier discrepancy disappear.

Evidence checklist

1. Match the exact apostrophe and Betsoft provider.
2. Confirm the 3-4-5-4-3 geometry and 720 ways.
3. Read the active 95.14% RTP value.
4. Capture the full claw award table.
5. Resolve 96 versus 98 for the deployed build.
6. Record retriggers against the 240 total ceiling.
7. Keep Shaman scatters separate from ways wins.
8. Preserve round ID, counters and closing balance.

FAQ

What RTP does Betsoft publish?

The official Tiger’s Claw page states 95.14%.

How many ways are available?

Betsoft lists 720 ways on a 3-4-5-4-3 reel layout.

Is the initial free-spin maximum 96 or 98?

The provider page contains both figures in different sections, so the deployed Help must resolve the conflict.

What is the total free-spin ceiling?

Betsoft states that retriggers can take the feature to 240 free spins in total.

How do Shaman symbols pay?

Three or more scattered Shamans pay from 2× to 50× total wager.

Is access in New Zealand verified?

No. That requires operator-level evidence.

Sources

• Betsoft, Tiger’s Claw, 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.