Touchdown Wins by PG Soft: multiplier growth and RTP guide

Touchdown Wins appears in PG Soft’s API as ID 2152563 and code touchdown-wins. The official description specifies three reels with two rows on reels one and three and three rows on the centre reel. Wins activate multipliers, and a randomly triggered eight-spin feature doubles all multipliers.

The catalogue record checked on 8 October 2026 publishes maximum RTP of 96.74%, a 5,000x headline maximum and feature multipliers up to 2,048x. Those are supplier maximum fields, not guarantees for every deployment.

Verified record

Field	PG Soft API
Catalogue ID	2152563
Code	touchdown-wins
Layout	3 reels; 2–3–2 rows
Maximum RTP field	96.74%
Headline maximum	5,000×
Free Spins	8, randomly triggered
Feature multiplier	Up to 2,048×
Feature modifier	All multipliers doubled

The description does not disclose the complete paytable, win-line geometry, stake range or volatility. Verify those in live help.

Asymmetric grid

The centre reel has three positions while the outer reels have two each. Capture all seven cells and the exact win route. Do not flatten the layout into a standard 3×3 grid.

Live rules must show whether wins follow fixed lines, patterns or another method. A football theme does not define settlement.

Win-activated multipliers

PG Soft states that wins activate multipliers. The retrieved description does not expose starting values, positions, persistence or growth sequence. Those must not be invented.

For each round, record the multiplier state before the win, qualifying combination, activation and resulting value. If several activate, use the live combination rule.

Random Free Spins

Eight Free Spins may be triggered randomly. This means a visible Scatter count is not established by the catalogue summary. Capture the parent round and system message when entry occurs.

Random entry is not a predictable event. Do not describe a near-touchdown image or previous losses as increasing its chance.

Doubled multipliers

During the feature, all multipliers are doubled. Record the pre-feature or base value and the doubled display. Do not double the resulting win a second time if the server has already applied the factor.

The official headline says factors can reach 2,048x in Free Spins. Confirm whether this is a single multiplier ceiling or combined result field in live help.

Maximum RTP

The API’s maximum RTP field is 96.74%. An operator can use another allowed profile. Record the percentage shown inside the launched game with version and date.

Do not describe 96.74% as session return. It is a long-run theoretical value for a configuration.

5,000x headline cap

The catalogue lists 5,000x as the headline maximum. This is distinct from the 2,048x feature multiplier. A multiplier acts on a win; the maximum limits the overall award relative to the defined bet.

Check the cap procedure and denominator in live rules. Neither number indicates frequency.

Paytable and route evidence

Capture the full symbol table and every permitted route. The asymmetric middle position can create patterns that cannot be inferred from an ordinary three-reel game.

For a sample win, document symbols, route, base award, activated multiplier, feature doubling if applicable and final credit.

Stake and currency

The API record does not establish minimum wager, maximum wager or NZD support. Use the active interface to record total bet and currency.

Do not calculate 5,000x or 2,048x from a deposit. Apply only to the unit defined in help.

Mobile evidence

On mobile, ensure all seven positions, multiplier states, balance, total bet and Free Spins counter remain visible. The centre cell must not be hidden by controls.

Test orientation and interruption with preview credit. Compare resumed values with server history before continuing.

Round ledger

Start with opening balance, stake, ID and seven-cell grid. Record ordinary route payment, each activated multiplier, any doubling and final settlement.

For the random feature, add the entry message, eight-spin counter, child rounds and final feature total. Sum each child credit once.

Source boundaries

The API confirms identity, geometry, maximum RTP, maximum win and headline feature. It does not prove operator access or detailed arithmetic.

Live help supplies deployed rules; operator terms supply territory. Keep those claims attributed to the correct layer.

Version control

Store ID 2152563, code, catalogue timestamp, live version, language and operator. Compare route map, multiplier lifecycle, random trigger, RTP and cap separately after an update.

Do not backdate a new live RTP to older screenshots.

Common mistakes

Do not call the layout 3×3. Do not invent Scatters for a random trigger. Do not double an already settled feature win, and do not equate 2,048x with the total cap.

Avoid promising 96.74% at every operator or claiming a provider preview proves NZ real-money access.

Responsible plan

Random feature entry and multiplier growth cannot be timed. Set a loss ceiling and session duration before play, using full currency stake.

Stop at the boundary even after a near-score animation. Previous outcomes do not store progress toward another random trigger.

Questions for support

Ask for active RTP, wager range, route map, multiplier start and growth, 2,048x definition, random-trigger record and cap handling. Include the catalogue ID and round IDs.

For local access, consult operator territory rules. Do not circumvent restrictions.

Short answers

What is the ID? 2152563.

What is the layout? Three reels with 2–3–2 rows.

What is maximum RTP? 96.74% in the catalogue field.

How many Free Spins? Eight, with random triggering described by PG Soft.

What happens to multipliers? All are doubled during the feature.

Is NZ availability confirmed? No.

Final assessment

Touchdown Wins has a small but unusual grid, so precise route evidence matters. Its main audit path is ordinary win, multiplier activation, feature doubling and final cap.

The API gives useful headline facts. The live build must provide the missing route, stake and configuration details.

Seven-cell worksheet

Draw the outer reels with two cells and the centre reel with three. Copy the exact route map from live help and assign each permitted path a label. For every credited win, mark its three positions and ordinary award before multipliers.

This avoids two common errors: inventing nonexistent corner cells and assuming only straight horizontal routes. The unusual geometry is the reason a screenshot alone may be misleading.

Multiplier lifecycle

Record multiplier state at round opening, the win that activates it, the new displayed value and its use in settlement. If several multipliers exist, preserve their individual identities and the server’s combination rule.

During Free Spins, add a column showing the value before and after the feature’s doubling. Apply the doubled figure once. Compare the child-round credit with history before advancing the counter.

Random-trigger proof

When eight Free Spins begin, capture the system entry message and parent round. A random trigger may occur without the Scatter pattern readers expect from other slots, so the server event is essential evidence.

Do not estimate trigger frequency from a small sample. Record only occurrence, initial counter and settlement. At feature end, reconcile all eight primary spins plus any documented additions.

Cap and factor distinction

Maintain separate fields for largest observed multiplier, published 2,048x feature ceiling and 5,000x overall maximum. A multiplier can be below the cap while the underlying win changes the final amount.

If server calculation reaches the maximum, preserve the cap message and remaining feature state. Do not assume how unfinished spins are handled.

Mobile geometry check

At phone width, the centre third cell and route highlights must remain visible. Verify that the multiplier does not overlap the total stake or feature counter. Use browser zoom and reduced motion to test readability.

After app switching or rotation, compare the seven symbols, multiplier state, counter and round ID with history. Stop if the display cannot be reconciled.

Version-update protocol

Compare ID 2152563, code, RTP maximum, cap, layout, route map, activation, random feature and doubling rule one field at a time. Save one ordinary activation and one complete Free Spins sequence as reference.

If an operator later shows another RTP, label it by deployment and date. Never overwrite the API maximum without explaining scope.

Reader decision points

Before play, confirm live RTP, full stake, route map, activation order and access to server history. Check that random feature entry is described without claims of timing or inevitability.

The game’s compact screen can be readable, but only if its asymmetric geometry and multipliers remain explicit. Visual excitement should not replace arithmetic.

Seven-cell session card

Use a seven-cell diagram for every checked round: two positions on the first reel, three on the centre reel and two on the last. Add the active route label, opening multiplier, post-win multiplier, total stake and server round ID. This compact card prevents the 2–3–2 layout from being unconsciously rewritten as a standard nine-cell grid.

For a random Free Spins entry, connect the parent round to the eight-spin feature record and show each doubled multiplier beside the child spin that used it. The published 2,048x feature factor and 5,000x overall cap belong in separate columns. If the live interface does not expose enough information to complete the card, record that transparency limitation before considering another paid round.

Official and related sources

• PG Soft official catalogue
• PG Soft public catalogue API
• PG Soft 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 PG Soft, 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.