Legendary Sumo by Endorphina: trophy Joker and x2 feature guide

Legendary Sumo uses five reels, three rows and twenty-one paylines. Endorphina publishes 94.76% RTP, high volatility and a €0.21–€105 supplier stake reference. Three or more Imperial Golden Cup Scatters trigger ten retriggerable Free Games.

During Free Games, the Cup Scatter also acts as Wild. Winning sumo fighters receive a Golden Trophy and turn into Jokers, creating the sticky-state feature named in the provider FAQ. Wins are multiplied by two.

Published configuration

Field	Provider value
Grid	5×3
Paylines	21
RTP	94.76%
Volatility	High
Bet reference	€0.21–€105
Trigger	3+ Golden Cup Scatters
Initial feature	10 Free Games
Feature multiplier	×2

These facts describe the provider profile checked on 8 October 2026. They do not confirm New Zealand operator access, NZD limits or another deployment’s active RTP.

Base-game lines and symbols

The Red Mask is Wild and substitutes for ordinary symbols except Scatter. Regular combinations should be verified against the 21-line overlay and current paytable.

The official summary lists a red sumo as the top example at 143× base bet for five. It also describes a red sumo as an equal second-highest example at 48×, an ambiguous duplicated label. Do not silently repair that wording. Use the live symbol images and paytable to identify the two actual fighters.

Record line number, natural symbols, Mask substitutions and displayed credit. This preserves the official conflict instead of inventing a distinction.

Cup Scatter and ten Free Games

Three or more Golden Cups trigger ten Free Games. The feature can retrigger. Capture the initial Cup positions, opening counter and any Scatter award shown by the loaded paytable.

During Free Games the Cup also acts as Wild. It can still serve the feature state while substituting in lines according to current help. Keep the Scatter count and line substitution records separate.

For retriggers, capture the counter immediately before and after the Cup event. Do not assume a quantity based solely on the initial ten if live help uses another retrigger increment.

Winning fighters become Jokers

The provider says each sumo fighter in the winning team receives a Golden Trophy and turns into Joker. The FAQ describes Sticky Wilds, indicating that transformed positions persist within the feature according to the game rules.

Record the grid before settlement, the highlighted winning fighters, trophy placement and next grid. Mark the reel and row of every Joker. Do not turn losing fighters or non-fighter symbols into Jokers manually.

At each following spin, compare the Joker coordinates with the previous state. If a Joker moves, disappears or resets, the current help and screen should explain the boundary. Preserve evidence rather than assuming permanent stickiness across every retrigger or feature.

x2 feature settlement

Wins during the feature are multiplied by two. Record the line amount before the factor when the result panel exposes it, then the final credited amount. Do not apply ×2 again if the displayed paytable value already includes the feature factor.

A Cup acting as Wild and a trophy Joker can support the same line. They are substitution states, not separate cash prizes. The ×2 treatment belongs to the resulting feature win.

At completion, add free-spin credits and compare them with the summary and server history. Keep any trigger award separate until inclusion is confirmed.

A position-based feature ledger

Use columns for spin number, Cup count, retrigger, Mask positions, new trophy fighters, existing Joker coordinates, winning lines, pre-factor amount, ×2 and credit. A small grid diagram is useful when several Jokers persist.

Attach every row to the parent paid round. If a disconnect occurs, wait for history and the restored counter. Do not repeat play to reconstruct missing animation.

This ledger answers whether the correct fighters transformed, whether Jokers persisted and whether ×2 applied once. It does not attempt to test randomness or RTP from a short session.

Risk and Bonus Pop

Classic Risk is listed as an optional post-win mode. Its doubling decision is separate from the feature ×2 and must be recorded after the slot settlement.

Bonus Pop is listed but may not be available in every casino or jurisdiction. If visible, capture cost, conditions and any RTP disclosure. A purchase route does not prove natural trigger frequency.

Decline optional modes during the first rules audit. This keeps the Cup, trophy and Joker sequence readable.

RTP, volatility and stakes

The published 94.76% RTP is lower than many nearby Endorphina profiles, which makes exact version verification especially important. It is still a long-run theoretical setting, not a forecast for ten Free Games.

High volatility does not guarantee a large result. Persistent-looking trophies can encourage continuation, but no visual state makes future wins certain. Stop at the pre-set money and time limit.

The €0.21–€105 range is in euros and must not be relabelled as NZD. Record the live currency and total debit shown by the operator.

Mobile, demo and access checks

Endorphina describes mobile and tablet support and may provide a partner demo. Demo mode can show trophy persistence but does not prove real-money access or configuration equivalence.

On mobile, all fifteen cells, trophy markers, counter, multiplier, stake and history must remain readable. Test portrait and landscape so a bottom overlay does not cover sticky positions.

Save title, provider, version, RTP, currency, limits, domain and date. For a dispute, include round ID, trigger, position ledger and final summary while redacting personal data.

Common interpretation errors

• Confusing the Red Mask Wild with the Cup Scatter/Wild.
• Turning every visible fighter into a Joker.
• Treating trophy animation as a separate payout.
• Applying ×2 twice.
• Assuming Jokers persist beyond the published feature boundary.
• Resolving the duplicated red-sumo label without live evidence.
• Converting euro limits into NZD.

Resolving the two red-sumo descriptions

The public page repeats “red sumo” for both a 143× top example and a 48× equal second-highest example. That text conflict should be documented, not guessed away from artwork. Open the live paytable and capture the actual two symbol images, names if provided, and values.

Until that evidence is available, refer to the 143× and 48× entries as separate published examples with ambiguous labels. Do not merge them, average their values or assign a colour that the source does not support.

Trophy-state transition test

Choose an organically occurring feature win with one clearly identifiable fighter. Capture the grid before payment, the winning-line highlight, trophy award and following spin. The same reel-and-row coordinate should reveal whether the transformed Joker persists.

Repeat the observation when several fighters join the winning team. Record only the fighters included in the paid combination. Nearby matching symbols that are not on the highlighted line should not receive trophies unless the loaded help states a broader team rule.

Cup as Scatter and feature Wild

In base play, the Golden Cup’s verified role is Scatter. During Free Games it also substitutes as Wild. Label the same symbol by phase in the ledger: “trigger Cup” on the paid grid and “Cup Wild” when it supports a line inside the feature.

This phase change does not necessarily remove its ability to retrigger. Capture any three-or-more Cup event and the counter update. The result panel should reveal whether Cups also contribute line substitutions on that retriggering spin.

Combining Joker states with x2

Persistent Jokers increase substitution coverage, while ×2 changes the value of a settled feature win. They should be recorded in different columns. Count the winning lines supported by Jokers, then apply only the multiplier shown by the game.

Do not multiply by two for every Joker or every trophy. The public rule states that wins are multiplied ×2, not that each persistent position adds another factor. Verify one multi-Joker spin against history to confirm the deployment.

Feature-boundary checks

At the final free spin, capture the last Joker grid, closing summary and next base-game screen. Trophy Jokers should not be assumed to carry into the next paid spin. A retrigger extends the current feature, whereas a new paid trigger creates another feature state.

If the interface restores after disconnection, compare Joker coordinates and counter with the last saved frame. Report a mismatch using the parent round ID rather than starting another wager.

Respectful and responsible framing

The sumo theme is visual context, not evidence about Japanese sporting rules or real athletes. Editorial artwork and copy should avoid caricature and should not imply that a real tournament endorses the game.

Persistent trophies can make a feature feel as though it is building toward a guaranteed result. No such guarantee exists. Set a limit before play, stop at that limit and use demo mode for mechanical research when permitted.

Final assessment

Legendary Sumo requires position tracking. Cups trigger and later substitute, winning fighters become trophy Jokers, and feature wins use ×2. A chronological grid record explains the settlement better than the final animation.

The provider page supports the 5×3, 21-line profile, 94.76% RTP, ten-spin trigger and trophy feature. Current help remains decisive for exact sticky-state boundaries and the ambiguous symbol labels.

Official and related sources

• Legendary Sumo 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.