Sevens High — every second win upgrades a Seven

Sevens High by Quickspin builds its main feature around a visible sequence: a base-game win starts a Sevens Respin, each additional win is added to the total, and every second win upgrades another coloured Seven into a Wild.

Sevens Respin sequence

Any winning combination in the base game starts the feature. The reels respin and a new win continues the sequence; the feature stops when a respin produces no new win. The official page says new wins are added to the existing Total Win, so the sequence should be documented as one feature rather than unrelated spins.

Blue, green and red progression

The second win turns the Blue Seven Wild. The fourth win upgrades the Green Seven, and the sixth upgrades the Red Seven. This 2–4–6 order is the key rule to verify on the active help screen because it explains why identical-looking Seven symbols can behave differently at different stages.

Free Spins extension

During Free Spins, each Seven that turns Wild adds two spins. All three upgrades can therefore add up to six extra Free Spins. Once transformed, those Seven symbols remain Wild until the bonus ends.

Evidence limits

The public product page does not expose a readable RTP, stake range, complete paytable or confirmation that the title is available at a New Zealand casino. Those details must come from the deployed game help and casino account.

One sequence, not a collection of paid spins

A base-game winning combination starts the Sevens Respin feature. The following respin is part of that same sequence, and each new win is added to the displayed Total Win. No fresh stake should be deducted for a feature respin. Recording the entire chain under one round identifier prevents it from being mistaken for several unrelated paid rounds.

The first winning result establishes feature win number one. The next respin either produces another win and advances the counter or produces no new win and ends the feature. That ending condition is exact: visible Sevens, near-matches or previous upgrades do not continue the chain without a new credited win.

The counter determines symbol state. Win two upgrades Blue Seven, win four upgrades Green Seven and win six upgrades Red Seven. A reviewer should record the counter before and after every settlement.

Capturing the trigger result

Save the stopped base grid, every credited combination, stake, currency, balances and round identifier. Confirm that at least one valid winning combination is present. The feature does not require a particular Seven to start according to the accessible description; any base-game win initiates it.

Label the trigger as W1 in the sequence ledger. Record the Total Win immediately after the base settlement and the state of Blue, Green and Red Seven symbols before the first respin.

Do not count a promotional animation or uncredited scatter as the initiating win. The paytable and round history decide whether the trigger result qualifies.

The second win and Blue Seven

If the first respin creates a new credited win, the sequence reaches W2. The Blue Seven becomes Wild at this threshold. Capture the symbol before the upgrade, the transformation and the settled grid used for later respins.

The upgrade belongs to the active sequence. The source does not state that Blue Seven remains Wild in a later paid round after the feature ends. Reset the symbol-state ledger when the chain concludes.

A Blue Seven appearing on W2 does not itself guarantee W3. The next respin still needs a new credited win to keep the feature alive.

The fourth win and Green Seven

W3 continues the sequence without a newly published colour upgrade. W4 changes Green Seven into a Wild. This gap is why the win counter must be explicit: counting only transformations can hide the intervening result.

At W4, the active state contains both upgraded Blue and Green Sevens. Record which of those symbols participate in each evaluated combination, but do not treat their presence as an automatic award.

If the client appears to upgrade Green after a different count, first check whether the trigger win was omitted from the ledger. The original paid-spin win is W1 under the published sequence.

The sixth win and Red Seven

W5 again advances the chain without a new colour threshold. W6 upgrades Red Seven, leaving all three named colours in their Wild state for the remainder of the active feature.

The published progression stops at the sixth-win Red upgrade. Do not invent an eighth-win symbol, multiplier or jackpot because the even-number pattern continues arithmetically. Any rule beyond W6 requires live primary evidence.

A sequence can end before reaching Red. The absence of a sixth win is a completed feature outcome, not an incomplete game or a reason that another sequence must compensate.

A state table for every respin

Use columns for feature-win number, respin number, counter before settlement, credited combinations, Total Win before and after, Blue state, Green state, Red state and continuation decision. The final row should explicitly show “no new win” and feature termination.

Keep monetary accumulation separate from the count of wins. One respin can contain several paying combinations but still represent a single new winning result for the sequence unless the deployed help defines the counter differently. The interface counter is authoritative.

If animation cycles through line wins, avoid incrementing the feature counter for each highlighted line. Reconcile the final counter with round history.

Worked base sequence ending at W3

Suppose the initial paid spin produces W1. The first respin wins and creates W2, so Blue Seven upgrades. The next respin also wins, creating W3 without another colour change. A following respin has no new win and ends the feature.

The record contains three credited result states and one terminal no-win state. It does not claim Green should have upgraded because the sequence never reached W4.

This example explains the counter without assigning invented stake, payout or probability. Actual credits come from the deployed paytable.

Worked sequence reaching all upgrades

A longer example records W1 through W6. Blue changes at W2, Green at W4 and Red at W6. After W6, any continued respins retain all three Wild states until the first result without a new win ends the chain.

The reviewer copies the symbol-state map forward and reconciles Total Win after each successful respin. If the next result fails to pay, the feature closes even though all three colours are Wild.

Reaching W6 in one observed round does not establish a frequency. It documents only that completed sequence.

Free Spins use the same thresholds with an extra effect

During Free Spins, each named Seven transformation adds two spins. Blue at W2 adds two, Green at W4 adds two and Red at W6 adds two. The published maximum extension from these three upgrades is therefore six spins.

Record the main Free Spins counter immediately before the threshold result and after the two-spin addition. Keep the colour upgrade and counter change in the same event row so an animation is not counted twice.

The source states that transformed Sevens remain Wild until the bonus ends. This persistence boundary differs from the base respin chain and should have its own ledger.

Free Spins trigger remains a live-help field

The accessible product description explains the extension behaviour but does not expose a readable bonus trigger or starting allocation. Obtain those values from the exact deployed help and record the trigger grid.

Do not infer the trigger from the 2–4–6 progression. Feature wins control upgrades after the bonus has started; they do not by themselves explain entry.

If the live version offers retriggers beyond the two-spin colour upgrades, identify the separate rule and keep those added spins in a different ledger column.

Worked bonus counter example

Suppose a verified Free Spins round reaches its second feature win with Blue not yet upgraded. The Blue transformation occurs and the main counter increases by two. At W4, Green changes and another two spins are added. If the chain ends before W6, Red remains unchanged and only four extension spins have been earned through this system.

If W6 occurs later, Red changes and the final two-spin addition brings the colour-upgrade total to six. The counter record should show each addition when awarded rather than adding six at feature entry.

The example does not supply the undisclosed starting allocation or a cash result.

Total Win reconciliation

The provider says each new win is added to the existing Total Win. Record the displayed total after every successful state and calculate the difference from the prior row. That difference should reconcile with the combinations credited on the current grid.

Do not confuse the Total Win amount with the feature-win counter. A large monetary result advances the sequence once, just as a smaller credited result does, unless the live rules specify another counting method.

At feature end, compare the final Total Win with account history and the balance credit. Preserve the round identifier so support can locate the entire chain.

Paytable requirements

Obtain the evaluation pattern, symbol values, Wild substitutions and any special Seven restrictions from the deployed paytable. The product page describes progression but does not provide a complete readable settlement table.

For each respin, trace the valid combinations and identify any upgraded Seven that participates. A Wild upgrade has value only through those paytable rules; colour change alone is not a cash award.

If several line animations appear on one grid, reconcile their subtotal before advancing the feature-win counter.

RTP, stakes and maximum exposure

The public page does not expose readable RTP, minimum or maximum stake, default denomination, volatility figure or maximum exposure. Record those fields from the live information panel with title, provider, version, operator, currency and date.

If multiple RTP settings exist, publish only the one shown to the tested account. Do not combine numerical data from different deployments.

Six extra Free Spins is a duration rule, not a maximum-win statement. It cannot be used to derive RTP or a payout cap.

New Zealand availability

Quickspin’s global page confirms the title and feature description, not availability for real-money play in New Zealand. Verify operator country terms, registration eligibility, authenticated catalogue and successful launch.

New Zealand-dollar stakes, payment methods, withdrawals and identity checks belong to the operator. Source them separately and date the verification.

A demo or portfolio card is insufficient evidence. Do not advise bypassing market controls.

Mobile counter visibility

On small screens, the feature-win count, Total Win, respin state and Blue/Green/Red transformations must remain visible. Test portrait and landscape orientations and confirm that controls do not obscure the terminal no-win result.

After rotation or backgrounding, compare the restored counter, colour states, Total Win, balance and round identifier with server history. Pause if the client resumes at a different stage.

Reduced-motion mode should still indicate each threshold and settled symbol state without relying on a transformation animation.

Accessibility of colour progression

Blue, Green and Red cannot be distinguished by colour alone. Each Seven needs a textual or patterned identity, and the Wild state should be announced explicitly to assistive technology.

Keyboard focus should reach help, paytable, history and responsible-play controls. A screen reader should communicate the feature-win count and added Free Spins at W2, W4 and W6.

If those states are only visual, document the accessibility limitation separately from settlement correctness.

Support-ready evidence

For a missing upgrade, provide the complete sequence from W1, not only the disputed grid. Include title, version, operator, timestamp, stake, currency, balances, round identifier, every credited result and counters before and after the threshold.

For a bonus extension issue, add the Free Spins counter transition and colour state. Identify whether Blue, Green or Red reached its published threshold.

Share no password, one-time code, private key or seed phrase. Ask authenticated support to inspect server events.

Session controls and consecutive-win framing

The sequence counter can make a player want to continue until the next even-number threshold. Yet the respins themselves end automatically on a no-win result, and a new paid round starts a new risk decision.

Previous short sequences do not make a six-win chain due. Set stake, spending and time limits before starting and do not raise the next paid stake to chase a colour that failed to upgrade.

Use responsible-play controls offered by the operator. Mechanical knowledge supports accurate reading, not outcome prediction.

Publication checklist

• Count the initial paid-spin win as W1.
• Advance only after a new credited respin win.
• Upgrade Blue at W2, Green at W4 and Red at W6.
• End the chain on the first respin without a new win.
• Keep Total Win separate from the feature-win counter.
• In Free Spins, add two spins at each colour upgrade.
• Cap published colour-based extensions at six spins.
• Keep transformed Sevens Wild until the bonus ends.
• Source RTP, stakes and bonus entry from the deployed help.
• Confirm New Zealand access through operator evidence.

Editorial assessment

Sevens High has a transparent progression once the correct counter is used. W1 starts the sequence, W2 changes Blue, W4 changes Green and W6 changes Red. A no-win respin ends the feature regardless of how many colours have upgraded.

Free Spins add a second consequence to those same thresholds: two extra spins per colour and persistent Wild states until bonus end. A final-quality review therefore needs a chronological counter ledger, not a gallery of transformation screenshots. Numerical configuration and local access remain unconfirmed until the exact live version supplies them.

Maintaining the page after a version change

Retain the old verification date when a new deployment is checked. Compare the trigger, W1 counting rule, 2–4–6 thresholds, terminal no-win condition and bonus extensions field by field. If only RTP or stakes change, do not imply that the progression changed too.

Save the current help screen and one complete round record beside the updated version number. Conflicting third-party descriptions should not replace primary evidence. If the live counter treats the initial result differently from the published sequence, show both dated sources and request clarification before rewriting the threshold explanation.

This version history also protects readers from stale numerical claims. A feature rule can remain stable while operator configuration changes, and those two kinds of updates should appear separately in the article.

Frequently asked questions

What starts a Sevens Respin? Any base-game winning combination.

When does the feature end? When a respin produces no new win.

When does the Blue Seven become Wild? On the second win in the sequence.

When do Green and Red become Wild? On the fourth and sixth wins respectively.

Can Free Spins be extended? Yes. Each Seven upgrade adds two spins, up to six extra.

Is RTP confirmed by the public page? No readable RTP is exposed.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Sevens High

Bottom line: count feature wins in pairs; that sequence controls both Wild upgrades and the possible Free Spins extension.

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