Safari Sam payline and feature evidence guide

Betsoft lists Safari Sam as live from 18 March 2014. The official page confirms five reels, 30 paylines, 97.50% RTP, medium volatility and a 50.78% hit rate. It also mentions frequent free spins and a separate bonus round, but the accessible feature captions are empty.

That limitation matters. A reliable review can publish the mathematics and layout, while trigger counts, awards and bonus decisions must come from the active Help document rather than memory or another site.

Verified specification

Field	Official value	Live check
Listed date	18 March 2014	Build identity
Reels	5	Row configuration
Paylines	30	Route map
RTP	97.50%	Active profile
Volatility	Medium	Studio label
Hit rate	50.78%	Definition in Help
Free spins	Confirmed, rules not public	Trigger and count
Bonus round	Confirmed, rules not public	Entry and settlement

Payline audit

Open Help and capture all 30 routes, pay direction, minimum matching length and symbol values. Number reel positions, then trace each winning line on the stopped grid. A symbol can belong to several paylines, so the award banner alone is not enough to reconstruct settlement.

Record Wild and Scatter exclusions exactly as shown. The public page does not expose them in text, and a standard five-reel layout does not prove a standard substitution rule.

Keep stake, line award and total round credit in separate columns. If several lines pay simultaneously, list them separately before comparing the sum with history.

Free-spin evidence

The provider confirms free spins but not their public trigger or starting count. Capture the triggering symbols, coordinates, awarded spins and any multiplier or reel change from live Help.

Number every feature spin. Record added spins only when the rules or counter demonstrate a retrigger. Do not infer a retrigger because the animation pauses or because a similar Betsoft title allows one.

At feature end, compare the spin-level subtotal with the credited result. Confirm that ordinary reels and counters return for the next paid round.

Bonus-round record

Treat the bonus round as a separate state. Save its entry screen, instructions, available actions and starting value. If the user makes selections, record each selection and outcome in order. If the round is automatic, avoid describing it as skill-based.

The accessible Betsoft page does not state the trigger, choice count, prize table or stopping rule. Those fields remain unavailable until the deployed instructions are captured. A trailer is supporting visual evidence, not a substitute for rules.

After completion, reconcile the bonus award with game history and final balance. Preserve the round ID so support can distinguish a display issue from settlement.

RTP and hit rate

The 97.50% RTP is a long-run theoretical return for the published profile. Medium volatility is a distribution label, while 50.78% hit rate can include awards below stake. It is not a 50.78% chance of profit.

A short test can verify paylines and feature flow but cannot validate the long-run percentage. Do not publish a personal sample as performance evidence.

Mobile and interruption checks

On mobile, confirm all five reels, 30-line selector, Help table and feature counters remain readable. Important symbols should have shapes or labels rather than colour-only distinctions.

Interrupt only after a settled result. Reopen and compare remaining spins, bonus state and balance with history. Replayed animation should never be counted as a second award.

Responsible review boundary

The provider page does not prove New Zealand or 22Bet availability, mobile deployment, stake limits, maximum win or a locally accessible demo. Those require a dated operator-level check.

Set a money and time limit before play. A high hit-rate label does not mean losses cannot accumulate, because small returns may still count as hits.

Evidence checklist

• Match Safari Sam, Betsoft and the 2014 edition.
• Confirm 97.50% in active Help.
• Capture all 30 paylines.
• Record pay direction and symbol values.
• Save Wild and Scatter exclusions.
• Document the free-spin trigger and starting count.
• Record every retrigger only from Help.
• Preserve the bonus entry and instruction screen.
• Log choices and outcomes separately.
• Reconcile both features with round history.
• Leave undocumented limits unavailable.
• Do not claim local access from the provider catalogue.

Worked session sheet

Create a header with title, provider, version, currency, stake and round ID. Under it, list each paid line and award. When a feature starts, open a nested table rather than continuing the base-game row.

For free spins, use one row per spin. For the bonus round, use one row per decision or automatic stage. At the end, compare the feature subtotal, base award and final credit. This exposes missing or duplicated values without guessing how the animation works.

Reconstructing undocumented features

When the public card names a feature but omits its rules, begin with identity rather than outcome. Capture the Help title, provider, version and build label if available. Save the trigger page, feature instructions and paytable in one session so an old screenshot cannot be paired with a newer configuration.

For free spins, record trigger count, coordinates, opening counter, changed reels, Wild behaviour and final settlement. For the bonus round, add entry condition, selections, prize units and exit rule. A promotional image supplies none of those facts. If Help uses icons without text, preserve its legend and accessible labels. Never infer equal probabilities from equal-looking choices.

Paytable change monitoring

Older titles can appear through several integrations. Recheck RTP and paytable whenever domain, currency or account territory changes. Store every capture with territory, date and source. If 97.50% is absent or another profile appears, report both only when their scopes are clear.

Compare values in stake units before currency. Rounding can make equivalent tables look different. Check whether line bet, total bet or coin value drives the award. Update the article when a stable primary source changes, not when an aggregator republishes an undated figure.

What the hit rate does not say

The 50.78% figure does not disclose average hit size, free-spin frequency, bonus frequency or chance of profit. A hit can return less than stake. Count settled paid rounds and separate feature entries without presenting a short sample as probability data.

Support-ready evidence

For a disputed round, retain timestamp, title, round ID, stake, balances, Help screenshots and the disputed stage. Describe the expected result from the active rules. Server history is stronger evidence than animation alone. Keep original files untouched and redact unrelated personal information from copies.

Reader decision points

Before proceeding, confirm the exact 2014 title, the published RTP in Help, all 30 understandable lines and readable feature terms. If any answer is no, pause rather than treating this review as a substitute for missing in-game disclosure. The same test applies on mobile.

A practical pre-session check

Before committing a stake, confirm that the loaded title is Safari Sam by Betsoft and not a similarly themed game. Open Help, capture the displayed RTP, total line count, coin or stake controls and every feature page available in that build. If the operator supplies a revision identifier, retain it beside the date. This short check connects the 2014 catalogue record to the software actually loaded in the account.

Next, set a fixed session limit without using the 50.78% hit-rate figure as a budget guide. That percentage does not state how many results will exceed the stake, how soon a bonus will arrive or whether a particular session will finish ahead. Medium volatility is also a broad studio label rather than a timing forecast.

If a feature activates, record the triggering screen before pressing through any animation. Note the stake, round ID, opening state, each awarded step and final credit. The product page confirms the presence of free spins and a bonus round but does not expose enough public rules to reconstruct either from memory. A dated Help capture is therefore more valuable than an undated video or third-party summary.

This method leaves a clean result: catalogue facts remain confirmed, build-specific rules remain attached to the build, and fields that cannot be observed stay marked unavailable. It also gives support a precise timeline if the on-screen sequence and account history do not agree.

Verdict

Safari Sam has a strong official statistical record but sparse public feature documentation. The honest review is therefore precise about RTP, hit rate, volatility and paylines while treating free-spin and bonus details as live-Help tasks.

That boundary is more useful than repeating unverified rules from aggregators and protects the original 2014 version from later configuration drift.

FAQ

What RTP does Betsoft publish?

97.50%.

How many paylines are listed?

Thirty.

Are free spins confirmed?

Yes, but their full public rules are not exposed in accessible text.

Is the bonus round documented completely?

No. Use the current in-game Help.

Is New Zealand access confirmed?

No.

Sources

• Betsoft, Safari Sam, 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.