The Exterminator rules and missing-feature evidence

The Exterminator is listed by Betsoft as live from 25 April 2013. The studio verifies five reels, 30 paylines, 96.27% RTP, low volatility and a 15.35% hit rate. Its public feature gallery labels a main game, Big Win and Wild image, but supplies no readable feature rules beneath them.

That evidence gap is important. It would be easy to fill it with remembered rules from old reviews, but those may describe another build. This page keeps unidentified triggers, symbol values, stake limits and maximum win unavailable until current Help is inspected.

Verified versus unavailable

Field	Status	Value or action
Listed live date	Verified	25 April 2013
Reels	Verified	5
Paylines	Verified	30
RTP	Verified at studio level	96.27%
Volatility	Verified	Low
Hit rate	Verified	15.35%
Wild rules	Unavailable in public text	Read Help
Bonus triggers and maximum	Unavailable	Do not infer

Why low volatility and low hit rate can coexist

Low volatility describes the distribution of awards, not how often any credit appears. A 15.35% hit rate means the provider’s model records hits less frequently than one might expect from the label alone, and a hit can still be below the stake.

Neither figure predicts the next round. Do not translate 15.35% into a schedule or assume a result is due after several losses. Short sessions can differ sharply from theoretical behaviour.

The 96.27% return is a long-run model figure. Confirm it in the deployed Help; if another percentage appears, preserve both with version, date and scope rather than averaging them.

Thirty-line reconstruction

Open the line diagram and record whether all 30 paths are fixed, where evaluation begins and the minimum matching length. For each test result, trace symbol positions across the five reels and compare the line award with history.

Save denomination, line stake and total stake. A paytable in credits cannot be converted to currency without the active credit value, while a line-bet multiple must not be presented as a total-bet multiple.

The public page does not state the grid height. Capture the full deployed grid rather than assuming a standard 5×3 arrangement from artwork.

Wild evidence protocol

The gallery confirms that a Wild exists but not what it replaces, where it can land or whether it pays on its own. Capture its full Help entry and every exclusion.

On a Wild-assisted result, record the natural symbols, Wild position, route and base paytable value. If the Wild carries a multiplier or expands, that must be visible in current rules before being published.

Do not use a “Big Win” gallery caption as proof of a formal mechanic. It may describe only an example screenshot or celebration screen, not a separate feature.

Building the missing paytable record

Capture each symbol row at readable resolution: two-, three-, four- and five-symbol values where available, Wild, scatter, bonus icons and award units. Keep the Help revision and game ID with the screenshots.

If the client uses multiple pages, preserve their order. An image-only table should be transcribed twice and compared to reduce digit errors. Any unreadable value stays unavailable.

Check whether the paytable changes with coin level or active lines. Never combine a symbol table from one operator with the 96.27% figure from another deployment.

Feature discovery without guessing

Before a permitted preview round, scan Help for free spins, pick bonuses, gamble controls and autoplay. Record only named mechanics. A raccoon or catcher animation may be decorative rather than part of settlement.

If a feature appears, preserve its trigger screen, instructions, state changes and final credit. One observed round can confirm order but cannot estimate probability.

Use server history when animation and wallet movement differ. Ask support for a detailed event log if the component award cannot be reconciled.

Round ledger

Record opening balance, currency, denomination, active lines and total stake. After the spin, save the grid, each line win, any feature state, total credit, round ID and closing balance.

The expected equation is opening balance minus stake plus settlement equals closing balance. Keep promotional balance separate if the operator uses one.

An interruption should not prompt another wager. Reopen history and match the existing round first. A replay can start midway through animation even when the server result is final.

Mobile and accessibility checks

At 390-pixel width, verify all reels, total stake, balance, Help and history. The 30-line map should remain readable through zoom or scrolling without losing line numbers.

Wild and ordinary symbols should differ by shape as well as colour. Reduced motion must leave a numerical settlement, and promotional controls must not obscure the spin area.

Test portrait and landscape before a paid round. If orientation resets Help or stake, document the behaviour and return to a stable layout.

Demo and New Zealand scope

Betsoft links an official demo. Sponsored links in this guide are commercial routes, not that demo. Studio documentation does not prove New Zealand access or listing at 22Bet.

Check the authenticated catalogue, territorial terms and exact loaded title independently. Report an account-specific result with date rather than a national conclusion.

Who may prefer this format

The Exterminator may suit readers looking for a classic fixed-line title with low-volatility classification. Its public transparency is limited compared with newer Betsoft pages.

Readers who need a fully documented feature list before launch should wait until live Help can be inspected. Absence of public detail is a limitation, not permission to improvise.

Evidence checklist

Minimum evidence package for an older title

An older product page with blank feature captions needs a stronger deployment record than a modern page with complete rules. Begin with one screenshot containing the full title, Betsoft attribution, game ID and Help revision. Add separate captures for RTP, line map, symbol table, Wild entry and every named feature page.

Create a transcription sheet with a source image reference beside every number. Paytable rows should identify symbol, matching count, award unit and any reel restriction. Do not copy a value when a digit is blurred; mark it unreadable and retake the image at a larger scale.

Next inspect menu controls without starting a paid round. Record autoplay, gamble, sound, speed and history options only as interface facts. They are not game features unless they affect settlement. The provider’s “Big Win” screenshot should remain a presentation label unless Help defines a threshold or separate award.

During one permitted test, compare total stake with the wallet deduction and preserve the final result. If a Wild contributes, annotate the exact substitution. If another special symbol appears, use the wording from Help rather than inventing a name from the artwork.

For any bonus transition, record the initiating symbols, their location, the instruction screen and the final credit. Do not estimate frequency from the sample. The purpose is to confirm calculation order and evidence recovery, not to reverse-engineer the RNG.

Store the package with territory, operator domain, currency and check date. This stops an old Flash-era rule set or another market’s configuration from being treated as universal. If support supplies a missing answer, retain the dated reply and quote only the factual rule.

The result can remain useful even when several fields are unavailable. A precise statement that the official public page confirms structure but omits feature rules is more trustworthy than a complete-looking table assembled from unrelated affiliates.

Recheck the public page and deployed Help on the same day whenever possible. If the client still runs while the catalogue has changed, record both timestamps rather than assuming one source is wrong. A support answer should identify the exact title and game ID; a generic statement about Betsoft slots cannot fill a game-specific evidence gap.

Finally, compare the mobile and desktop Help panels. Older titles sometimes expose complete rules in one interface but truncate them in another. Prefer the clearest primary capture, while noting the device and build used.

Archive both views when their wording or values differ materially.

Record the client version shown beside each capture.

1. Match exact title and provider.
2. Confirm 96.27% RTP.
3. Capture 30 line paths and grid height.
4. Transcribe the complete paytable.
5. Document every Wild exclusion.
6. Treat Big Win as a caption until rules say otherwise.
7. Preserve round ID and wallet movement.
8. Mark unknown features unavailable.

FAQ

What RTP does Betsoft publish?

96.27%.

How many paylines are listed?

Thirty across five reels.

What is the volatility?

Betsoft classifies it as low.

Are full bonus rules public?

No. The accessible product text does not describe them.

Is a Wild confirmed?

Yes, through the official gallery label, but its substitution rules require live Help.

Is New Zealand access confirmed?

No. Operator-level evidence is required.

Sources

• Betsoft, The Exterminator, 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.