Twerk by Endorphina: Dance Battle rules and paytable evidence

Twerk is a three-reel, three-row slot with five fixed paylines. Endorphina publishes 96.05% RTP, high volatility and a €0.05–€75 reference range. Three VS Scatters open a Dance Battle made of five rounds, where a randomly selected dancer competes against others through special reel outcomes.

This article uses the supplier page checked on 8 October 2026. It does not claim that a New Zealand operator carries the title, that a particular account can use Bonus Pop, or that euro limits translate into NZD.

Published configuration

Field	Official value
Grid	3×3
Paylines	5 fixed
RTP	96.05%
Volatility	High
Supplier stake reference	€0.05–€75
Trigger	3 VS Scatters
Bonus structure	Dance Battle across five rounds
Risk feature	Listed
Bonus Pop	Listed; availability may vary

The compact grid makes the game easier to map than a large ways system, but it does not remove the need to verify each line. Five fixed paths still have defined shapes and settlement rules.

Five-line base game

Open the payline overlay and copy the route for every highlighted win. Three identical pictures appearing anywhere on the grid are not automatically a combination. They must occupy consecutive positions on one of the five enabled paths.

The official symbol notes use “base bet”. That phrase may refer to a unit other than the total stake shown by an operator. Record the denomination, total debit and currency before converting a multiplier into cash. Use the server’s credited amount as the final account-level result.

VS Scatter and entry payment

The VS picture acts as Scatter. Exactly three trigger the Dance Battle and the provider says three also pay 5x base bet. Preserve the trigger grid so the direct award and bonus entry can be reconciled independently.

Do not describe the five-round event as ordinary Free Spins without qualification. Endorphina presents it as a battle with a restricted symbol set and a progression condition. That structure deserves its own ledger rather than being merged into the normal reel sample.

How the Dance Battle works

When three VS symbols land, the game randomly chooses a dancer. The battle reels then contain symbols for the competing dancers plus VS. Each battle is divided into five rounds, and the winner is the dancer who gathers the greater number of winning lines.

Endorphina says all wins are credited regardless of which dancer produced them. If the selected dancer wins the battle, the player receives bonus prize money and advances to the next battle. That means line credits, battle result, bonus prize and progression are distinct events.

For every round, record the competitor symbols, lines won by each side and currency credits. After round five, save the tally, declared winner, bonus award and whether another battle opens. This timeline is more reliable than interpreting the choreography.

Random selection does not create control

The dancer is selected by the game, not by player skill. A theme that resembles a contest does not make the outcome skill-based. The line results remain governed by the game’s random process, and no choice of timing or screen interaction can guarantee progression.

Avoid language such as “beat the opponent” unless it is clearly describing the game’s presentation. For audit purposes, the relevant facts are the five recorded rounds, line totals and server settlement.

Published symbol hierarchy

The gold twerk symbol is identified as highest-paying, with three paying 100x base bet. Black shorts follow at 20x for three, and ripped shorts at 10x. The VS Scatter pays 5x for three while also opening the feature.

These are selected headline values, not the complete paytable. Copy any one- or two-symbol rules, alternate awards and line directions from the current help. Do not infer them by halving the published three-symbol values.

RTP and high volatility

The provider publishes 96.05% RTP for the referenced product page. It is a long-run theoretical value, not the expected outcome of one battle or session. Endorphina does not show a public list of alternate RTP configurations on this page, so the loaded help must be checked separately.

High volatility signals uneven result distribution. It cannot show when three Scatters will appear, whether the selected dancer will advance, or how much budget is required. A sequence of losses does not make a bonus due.

Euro range versus account stakes

The €0.05–€75 range is supplier metadata. It neither proves New Zealand access nor defines an NZD limit. If the title appears at an operator, open the stake selector and record currency, minimum, maximum and increments before play.

Use total debit per round when setting a spending limit. Battle animations can lengthen session time without changing the amount already committed to the triggering spin, so track money and time independently.

Risk Game and Bonus Pop

The official feature list includes a Risk Game. If offered after a win, treat it as a new decision: preserve the original credit, amount risked, available choices and final result. Do not rewrite the original reel settlement after the risk outcome.

Bonus Pop may provide paid access to a feature in eligible deployments. If visible, capture its cost, entry state, confirmation text and any RTP disclosure. The presence of the tag on a provider page does not prove that the control is legal or enabled in every region.

Mobile and demo checks

The official page says the game is available on mobile devices. Test whether the 3×3 grid, five paylines, VS count, battle tally, total stake and balance remain visible without accidental taps. Landscape mode may provide more room for the two competitors and progression display.

A demo can teach the five-round order but cannot establish real-money access or current local terms. Compare demo title, RTP and version with the operator help before relying on it.

Worked battle ledger

Begin with the triggering round: three VS symbols, any 5x Scatter payment and opening balance. For each of the five battle rounds, create columns for selected dancer lines, opposing dancer lines, other line wins and currency credited.

After the fifth round, total the competition lines without adding them again to the currency result. Record the named winner, bonus prize and next state. If the chosen dancer advances, start a fresh five-row section for the next battle instead of extending the first tally indefinitely.

Connection and interruption cases

If the browser closes during a battle, do not replay from screenshots or assume unfinished rounds were lost. Reopen the account history and locate the parent round plus any child events. The server record should show the settled line credits, battle decision and continuation state.

Save timestamps before contacting support. Ask whether the displayed bonus prize is included in the battle total and request the authoritative round log. A complete ID chain is more useful than a screen recording without identifiers.

Distinguishing points from money

The battle presentation uses winning lines to decide which dancer wins, while the account balance records currency. Those two measures must not be merged. A competitor can lead the battle tally even when another line carries a larger monetary award, depending on how the current rules count points.

Build two columns for every round: battle lines and settled credit. Sum the first only to verify the winner; sum the second only to reconcile the balance. If the interface uses another scoring unit, copy its label exactly. Do not convert points into cash or assume one point equals one base bet.

The advancement prize also needs its own row. Record whether it appears as a separate credit, is included in the final battle total, or only unlocks another stage. This distinction prevents a competition result from being counted once as line wins and again as a supposed cash bonus.

Evidence pack

Keep title, provider, active RTP, currency, stake, UTC time, round ID, opening balance, trigger grid and closing balance. Add the selected dancer, five individual rounds, line tallies, all credits, battle winner, bonus prize and advancement status.

Redact account identity and payment information from public copies. The support channel may require authentication, but an editorial report should not expose private records.

Editorial treatment of the theme

The official artwork and description use suggestive dance imagery. This page replaces it with an empty professional studio and discusses only mechanics. It does not sexualise performers or claim that the theme affects mathematical results.

The provider page supports the grid, five lines, RTP, volatility, trigger, battle sequence and selected symbol values. It does not establish an operator listing in New Zealand, local limits or a maximum-win figure.

Final assessment

Twerk’s distinctive mechanic is not merely “five Free Spins”; it is a five-round comparison where line totals decide whether a randomly selected dancer advances. Keeping competition points separate from currency credits is essential.

Use the official 96.05% RTP as a dated supplier reference, verify the deployed build and record the battle chronologically. A compact grid makes the evidence easier to collect, not the outcome easier to predict.

Official and related sources

• Twerk official product page
• Endorphina catalogue guide
• Responsible gambling guide
• Corrections policy

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