Under The Sea rules and paytable-verification guide

Under The Sea is listed by Betsoft as live from 9 August 2012. The official product page confirms five reels, 30 paylines, 96.40% RTP, medium volatility and a 54.51% hit rate. It labels main-game, Scatter and free-spin imagery, but the accessible feature descriptions are blank.

This review therefore does not invent the Scatter trigger, feature count, Wild rules, stake range or maximum. Those details need the exact deployed Help or another primary Betsoft document.

Verified and unavailable fields

Field	Status	Official value
Release listing	Verified	9 August 2012
Reels	Verified	5
Paylines	Verified	30
RTP	Verified	96.40%
Volatility	Verified	Medium
Hit rate	Verified	54.51%
Scatter	Feature label verified	Trigger unavailable
Free spins	Feature label verified	Count unavailable
Stake and maximum	Unavailable	Requires live Help

What the numbers do and do not say

RTP 96.40% is a theoretical long-run value for the studio specification. It is not a session refund. A 54.51% hit rate may include awards smaller than the stake and should not be read as a probability of finishing ahead.

Medium volatility describes distribution broadly. It does not tell a reader when the Scatter will land or how many spins a feature will last. Those probabilities are not published on the accessible page.

When the client displays a different RTP, retain both sources with version and date. Do not average configurations or assume the studio page overrides the loaded Help.

Recovering 30 payline patterns

Open the paytable and save every route. Determine whether all lines are active at every stake and whether symbol values use line bet, coin value or total bet. Without that denominator, a multiplier cannot be converted into currency.

Trace a sample award from the required starting reel through adjacent reels. Similar fish elsewhere on the grid are irrelevant if they do not follow a valid pattern. Save the line-highlight view and round history.

The product page does not publish symbol values. Decorative pearls, fish and mermaid imagery should not be assigned paytable roles merely from the overview.

Scatter evidence

The official page labels an image as Scatter but gives no accessible rule text. A complete record must identify the Scatter symbol, eligible reels, minimum count, payment method and whether it triggers free spins.

Do not assume three Scatters are required simply because that is common. Do not let a Wild substitute unless Help explicitly permits it. Record whether Scatter awards depend on total bet and whether they pay anywhere or only on lines.

If the symbol is an oyster or pearl in the artwork, confirm that label in Help. Theme-based identification is not enough for a numerical claim.

Free-spin evidence

The page also labels a free-spin image, proving the mode exists at product level. It does not state the opening count, retriggers, multiplier, special reel set or persistence rules.

Capture the trigger page, counter before the first spin, every modifier and the final summary. If the feature is entered from the Scatter, preserve the triggering grid and its separate award.

A trailer can illustrate appearance but cannot replace written rules. Pause-frame interpretation is especially risky when animations add fish or pearls that are not settlement symbols.

A deployment worksheet

Begin with exact title, provider, Help version, operator, account territory, currency and check time. Add rows for RTP, total-stake range, line count, Wild, Scatter, feature trigger, free-spin count, retrigger and maximum-win clause.

For each field, store the value and source location. Use verified, uncertain or unavailable. A blank official page should remain unavailable until a stronger primary source is captured.

This worksheet keeps the 2012 studio listing separate from a modern operator wrapper. A redesigned interface does not necessarily change the underlying rules, but that equivalence must be verified rather than assumed.

Preventing confusion with similarly named games

“Under the Sea” is a generic theme used across the industry. Match Betsoft branding, exact title casing, release evidence and Help header. A mermaid or coral reef alone is not enough.

Keep aliases in internal notes but publish one canonical page for the Betsoft product. If an operator appends a version label, compare game ID and rules before deciding whether it belongs here.

Never transfer RTP or free-spin rules from another provider’s underwater title. Search similarity does not establish product identity.

Mobile and accessibility checks

At narrow width, the 30-line diagram, total stake and feature counter must remain readable. Fish symbols should differ by shape or label rather than colour alone.

Test reduced motion and muted sound. Scatter identification, feature start and final award should not rely solely on bubbles, camera movement or music.

If connectivity fails during free spins, use history to find the triggering paid round and final settlement. The replay may resume partway through the animation.

Stake and maximum restraint

The public page provides neither stake range nor maximum multiplier. Do not copy foreign-currency limits from an affiliate. Read the actual bet control and maximum clause.

Set a spending ceiling before launch. A comparatively high hit rate can still include many low awards and does not remove the risk of loss.

If Help cannot be opened, the sensible decision is to leave rather than rely on incomplete documentation. Transparency is part of product evaluation.

Demo and New Zealand boundary

Betsoft links an official demo. The sponsored routes here are not that demo. The studio page does not prove New Zealand real-money availability or presence at 22Bet.

Check territorial terms and an authenticated lobby. Record date and account currency for any successful launch, because catalogue access can change.

Who may use this guide

The guide helps readers distinguish verified studio metadata from missing feature rules. It may suit someone researching an older Betsoft title before opening the client.

It cannot support a full feature comparison until Help is captured. The correct editorial response to missing rules is restraint, not generic underwater prose.

Minimum publication gate for recovered rules

A new feature claim should not be added from a screenshot with no version context. Require the Help header, exact symbol legend, relevant rule paragraph and check date together. Numerical claims also need the stake denominator.

When only part of the feature is readable, publish that part narrowly. For example, a visible opening counter can prove the awarded spins in one deployment, but not the general trigger probability or every retrigger condition.

Keep the older verified fields intact when adding new evidence. Readers should be able to distinguish the studio’s public 96.40% record from any operator-specific profile discovered later.

Evidence checklist

A Scatter and feature verification card

The card begins with a full image and plain-language name for the Scatter. Record every reel on which it can land, whether it pays anywhere, the minimum count and each count’s award. Add a separate field for Wild substitution so a reader never assumes that an ordinary Wild can complete the trigger.

The next section records the relationship between Scatter and free spins. If the Scatter triggers the mode, note opening spins for every qualifying count, any direct Scatter payment and whether both are awarded together. If another symbol starts free spins, keep the two mechanisms separate.

During the feature, record retrigger requirements, added spins, multiplier changes, altered symbol sets and any sticky or expanding state. The public page confirms none of these details, so blank fields should remain visibly unavailable rather than being filled with common slot conventions.

Finish with a sample settlement: account currency, total stake, triggering grid, paytable factor, opening counter, final feature award and closing balance. Link all entries to one or more server round IDs. Remove personal identifiers before the evidence is stored editorially.

This card also prevents confusion with other underwater games. Title, Betsoft branding, Help version and product URL sit at the top; mermaid or pearl artwork is only a secondary identifier. If an operator uses a shortened title, compare the game ID and rules before treating it as the same product.

Recheck the card when the client updates. A changed thumbnail is presentation; a different RTP, trigger or maximum is a configuration or rules change and requires a dated new row.

1. Match exact Betsoft title.
2. Confirm 96.40% RTP in Help.
3. Capture all 30 line diagrams.
4. Identify the Scatter and its eligible reels.
5. Record trigger and free-spin count.
6. Verify retriggers and modifiers.
7. Capture stake range and maximum.
8. Preserve round ID and final credit.

FAQ

What RTP does Betsoft publish?

The official page states 96.40%.

How many paylines are listed?

The game has 30 paylines.

Is the Scatter rule available?

Its existence is labelled, but the trigger and payout are not readable publicly.

Are free spins confirmed?

Yes at feature level; detailed rules need live Help.

Is a maximum verified?

No.

Is NZ access confirmed?

No. Operator-specific evidence is required.

Sources

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