Perfect Strike: Trophy respins, random Free Spins and RTP

Perfect Strike is catalogue ID 2024510 and code perfect-strike in PG Soft’s English feed. The primary game-information document is version 1.0.r4, dated 26 March 2026. It describes a three-reel, three-row slot with five fixed lines, a locking Trophy respin and a separately random Free Spins event.

The PDF reports 96.76% theoretical RTP, medium volatility and a 4,000× maximum win. PG Soft’s API currently displays a 96.78% maximum-RTP field, producing a small source conflict. This page keeps both values visible instead of silently replacing the versioned rules figure.

Evidence table

Field	Verified record	Interpretation
Catalogue identity	2024510 · perfect-strike	PG Soft API
Rules revision	1.0.r4 · 26 March 2026	English PDF
Layout	3 reels × 3 rows · 5 lines	Standard reels
PDF RTP	96.76%	Versioned rules value
API maximum RTP	96.78%	Catalogue field checked 8 October
PDF RTP split	65.31% main · 31.45% Free Spins	Reference simulation
Overall hit rate	30.03%	PDF summary
Session volatility	Medium	Supplier label
Maximum win	4,000× bet	Formal ceiling
Default euro range	€0.25–€250	Reference, not NZ terms
Platforms	iOS, Android, HTML5, macOS, Windows	Technical list

The two RTP numbers should not be averaged. The PDF attaches 96.76% to version 1.0.r4; the API’s maxrtp field may describe a newer or alternative maximum profile. Only the deployed help can establish which percentage applies to a chosen account.

Base game and five lines

Perfect Strike evaluates five fixed paylines across the 3×3 window. The visual paytable shows the symbol awards and winning-line patterns at the selected wager. Because cash values scale with stake, capture the total bet and active line presentation together.

The simple geometry makes results easier to trace than a large ways grid, but it also makes the distinction between line symbols and Trophy collection essential. Trophy symbols drive their own respin process rather than behaving like an ordinary payline combination.

The reference bet model uses sizes 0.05, 0.5 and 5 with levels one through ten. Those inputs produce default euro totals between €0.25 and €250. An NZ integration can use different currency denominations, so the live wager panel takes priority.

Trophy respins

One or more Trophy symbols may appear on any paid spin. When at least three land anywhere, all reels respin while the existing Trophies remain locked in their positions. During the respin, only Trophy symbols can newly appear.

If one or more additional Trophies land, they lock and another respin follows. The process stops when a respin adds no new Trophy. The final award is based on the total number collected, with the supplier’s promotional summary indicating awards up to 200× for the collection table.

This is an open-ended reset sequence rather than a pre-announced number of spins. A round log should show the initial count, additions on each respin and the final collection size. Empty respins end the sequence; they do not erase already locked symbols.

Random Free Spins

During any main-game spin, the title can randomly trigger 10 Free Spins while the reels are spinning. This event is not described as a Scatter combination and should not be advertised as a choice available on demand.

Each free-spin win receives one of three documented multipliers: 2×, 5× or 10×. The factor applies to that win under the displayed feature state. Ten spins is the stated maximum starting quantity in version 1.0.r4; the document does not describe a retrigger.

The Trophy respin and random Free Spins are separate mechanics. A reader should not assume that collecting three Trophies starts the 10-spin feature or that the random feature guarantees a Trophy collection. The live interface should name the current mode clearly.

Reading the RTP discrepancy

The versioned PDF’s 96.76% is accompanied by a component split and simulation data, making it the more complete rules source. The public API’s 96.78% is explicitly a maximum-RTP catalogue field. Both are first-party facts but answer slightly different questions.

Before a paid decision, open help and record the exact percentage, build number and time. If the live game shows 96.78%, cite the deployed screen and treat the PDF as an older or alternate reference. If it shows 96.76%, the document aligns. Any other value needs its own dated record.

The PDF’s 30.03% overall hit rate combines 29.03% main game and 1.00% Free Spins. Hit rate counts winning events under PG Soft’s simulation method; it does not indicate average return per hit or predict how soon a random feature will appear.

Maximum and prize boundaries

The formal maximum is 4,000× the bet amount. Once accumulated winnings in the main game or Free Spins reach the cap, the spin ends. The Trophy collection’s 200× headline and a Free Spin’s 10× factor are component values, not alternative overall maxima.

If an interface continues celebratory animation after the cap, check history for actual settlement. The authoritative figure is the credited round total, not the duration of the visual sequence.

Mobile verification

The support list covers modern mobile and desktop environments and specifies 1080×2340 portrait presentation. On a phone, check that locked Trophy positions remain obvious without relying solely on colour, the respin state is announced, and the total stake remains visible during the animation.

Open the paytable at enlarged system text. The five line diagrams and Trophy collection table should fit without horizontal clipping. During Free Spins, the current factor and remaining count should not overlap the 3×3 board.

Test restoration by leaving the browser after a Trophy locks and returning. The same symbols and round ID should reappear or history should settle the final result. A wallet movement without a matching round record warrants stopping and documenting the discrepancy.

One-round audit method

Draw the nine positions and mark the initial Trophies. Create one line for each respin, showing new Trophy locations and running count. At the first empty respin, copy the final award from both the feature summary and history.

For random Free Spins, use a different sheet: spin number, raw line win, displayed multiplier, credited result and cumulative feature total. This prevents a 10× factor on one spin from being misread as a multiplier for the entire feature.

Availability and demo limits

The PG Soft catalogue confirms that Perfect Strike exists and supplies a provider redirect. It does not show whether a New Zealand account or 22Bet offers the game, whether NZD is supported, or which RTP profile is active. A preview is not proof of real-money territory access.

Autoplay, Turbo Spin, rules, history and verification controls appear in the reference guide. Operator policy may disable some of them. This review therefore describes support, not universal availability.

Checking the Trophy award table

The rules establish the trigger and collection sequence, but the visual paytable supplies the exact award for each final Trophy count. Open that table before playing and photograph the complete count-to-award ladder at the selected bet. A headline “up to 200×” is not a substitute for the intermediate rows.

After a respin sequence, match the number of locked Trophies with the corresponding table entry. Confirm whether the history expresses the result as a bet multiple or cash amount, and verify that it was not also counted as an ordinary line win unless the rules explicitly show both components. This prevents a common mistake in which the same on-screen Trophy is added twice.

If a version update changes the award ladder but retains ID 2024510, record the new rules revision and date. The stable catalogue identity does not freeze the paytable forever.

Support checklist for an interrupted feature

Perfect Strike’s small grid makes a concise evidence pack possible. Save the initial three-Trophy trigger, each later locked position, the first empty respin, the final award and wallet balance. Include the round ID and device time.

For a random Free Spins interruption, also capture the remaining-spin counter and active multiplier. Do not describe the event as “missing” until history has had time to settle; animation can reconnect after the server has already decided the result. If the final record remains absent or the credit conflicts with the recorded factor, stop further wagering and send the pack to support.

Bankroll interpretation without a promise

Medium volatility is not a stake recommendation. It does not define how many spins a balance will last, because stake size and realised outcomes dominate a short session. The random feature also has no countdown that makes it “due”.

A practical limit is chosen before opening the game and expressed in cash, not as a plan to continue until a Trophy sequence occurs. The session should end at that limit regardless of whether the last spin showed two Trophies or a near-complete line; near misses do not change the next random result.

Final assessment

Perfect Strike is mechanically direct: Trophies lock through repeated respins, while a separately random 10-spin feature applies 2×, 5× or 10× to winning spins. The important editorial issue is the first-party RTP difference between API and PDF.

That conflict does not make the game unverifiable; it defines the next check. A reader should match the deployed build and percentage rather than selecting the higher catalogue value. Identity, core rules and 4,000× cap are otherwise documented clearly.

Official and related sources

• PG Soft Perfect Strike game information PDF
• PG Soft official catalogue
• 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.