Explore the guides
Begin with the allocation rather than the headline count
A free-spin allocation is described by a count, an eligible game and a stake value. Those three fields belong together. A headline containing a large number of spins leaves the nominal stake total undefined when the stake per spin is absent. Start a comparison by identifying the allocation shown in the account or the exact campaign terms, then connect the count with the game version and its stated unit.
For example, twenty fictional spins at 0.10 units represent two units of nominal spin stakes. Twenty spins at one unit represent twenty nominal units. This arithmetic describes the allocation’s stake inputs. It does not identify the awards that the rounds will generate or the amount that may ultimately become withdrawable. Keeping the nominal allocation and the eventual account entries in separate columns makes the comparison much easier to read.
The allocation also has a source and a date. Record the campaign name and the place where the count was displayed. A public banner, an email and an account promotion area can describe different stages or editions. Connecting the allocation to one identifiable campaign prevents a comparison from borrowing an attractive count from one promotion and a more favourable stake value from another.
Identify the eligible title and version
The game identified by a free-spin campaign should be treated as a specific version, rather than every lobby entry sharing similar artwork. A campaign can name a title, a studio, a particular edition or a list of eligible games. Keep that identification in the allocation record. If the lobby contains several entries with the same name, the campaign’s own instructions are needed to identify which one applies.
The information panel can establish the rules and stake units of the loaded version. It may also show a configuration identifier. Record those details if they are available instead of relying on a review of a different edition. A familiar thumbnail is useful for finding a game, but the allocation’s actual eligibility and the game’s actual rules remain the relevant comparison inputs.
Where the game cannot be located, the support question should identify the campaign and the eligible title stated in its terms. A general message saying that free spins disappeared provides less context. Keep the distinction between an allocation missing from the account and an eligible game unavailable in the current edition. Those are different observations, even where the interface presents them through the same promotional area.
Read the stake value in its actual unit
A stake value can be shown in account currency or in game credits. The relationship needs to be explicit before the allocation can be compared with another one. A credit is a display unit, and its value can depend on denomination. A small number without its unit cannot support a reliable calculation. Record the complete stake value, denomination where relevant, and the account currency.
In a hypothetical game, ten credits at a 0.01-unit denomination represent a 0.10-unit stake if that is how the version defines its units. Another game might show 0.10 directly as the complete stake. The two displays could describe the same nominal input, but the connection comes from the rule and conversion, not from the appearance of the number. Preserve the original display in the record so the calculation can be reproduced.
If the campaign does not state the stake value, keep the nominal total unresolved. A comparison table can show the known spin count and identify the missing unit clearly. Filling the gap with the value used by another campaign would create an invented allocation. The useful next question asks for the stake attached to that exact promotion and game edition.
Keep count and nominal stake total separate
The count describes how many allocated rounds are available under the campaign. The nominal stake total multiplies that count by the defined stake value. These fields answer different questions and should have separate headings in a comparison. A reader can then see whether a larger count also represents a larger nominal allocation or simply divides a similar amount into smaller round stakes.
Consider two fictional allocations. One contains fifty spins at 0.10 units; the other contains twenty spins at 0.25 units. Each represents five nominal stake units. Their count differs, and the relevant games and resulting-balance rules can still differ. The matching nominal total is one descriptive observation, not a claim that the allocations produce equivalent results or have identical conditions.
Preserve each component when an allocation contains several stake values or stages. Multiplying the complete count by only the highest displayed stake would overstate the nominal total. Calculate each defined component separately and then add the component totals where a combined figure is useful. This method makes the arithmetic transparent and leaves the actual round awards and conversion conditions to their own part of the record.
Awards and nominal allocation are different values
A nominal stake total describes the inputs allocated to rounds. The awards generated by those rounds depend on their actual outcomes and the game’s rules. Multiplying spin count by stake is therefore not a forecast of winnings. The comparison should display a nominal allocation as such and preserve any resulting award record separately. This avoids turning a clear arithmetic input into an unsupported prediction.
The account may show a combined feature result or a total from several allocated rounds. Identify what the displayed total includes before adding it to other records. A running total can already contain earlier round awards. Adding those individual awards again would count the same result more than once. Where an allocation history or round history is available, use its identifiers to connect the values.
For a fictional record, a nominal five-unit allocation might produce a total award different from five units. That observation alone says nothing about a future allocation. The useful comparison concerns the actual treatment of the recorded award: where it is credited, what conditions govern it and which entry establishes its later status. These are questions about the condition set and the account ledger, rather than a promise about another sequence of rounds.
Locate the resulting balance entry
The campaign should identify how awards from the allocated rounds are credited. They may enter a promotional balance, a cash balance or another defined category under the actual terms. The label in a short banner may not explain the complete balance treatment. Record the account entry and the campaign condition that governs it so the connection is visible.
A combined account total can hide several balance types. A new total by itself may not show whether the awards were credited as conditional value or as another balance category. Ask which entry belongs to the exact allocation if the interface does not make it clear. Keep any credited amount separate from the nominal stake total and from unrelated deposits or withdrawals.
A useful support question names the allocation, its eligible game and the missing or disputed resulting-balance entry. This is different from asking why a bank payment has not arrived. The allocation’s crediting process, any later conversion and an outbound withdrawal are separate stages. Maintaining that sequence makes it possible to resolve one stage without incorrectly declaring that every later stage has also been completed.
Apply any wagering base to the correct amount
A requirement attached to free-spin awards needs its exact base and multiplier. The base might be the amount arising from the allocation or another value defined by the campaign. The nominal stake total is not automatically that base. Record the wording used by the promotion before performing any multiplication. A calculation with the wrong starting amount can look precise while describing a condition that does not apply.
Suppose a fictional allocation produces an eight-unit promotional award and the terms define twenty times that award as the requirement. The resulting qualifying-stake total is one hundred and sixty units under those fictional inputs. This example explains the base calculation. It does not predict the awards from an allocation, the cost of completing a requirement or the balance remaining afterwards.
If the campaign has several components, identify whether each component creates a separate requirement or whether the terms define a combined base. Keep the allocation and credited award references with the calculation. A general brand FAQ may describe a different campaign, so its multiplier should not be silently substituted for the missing rule. The exact condition set is the authority for that calculation.
Contribution determines counter advancement
Eligible game contribution determines how much an action advances a requirement. That proportion is separate from the game’s RTP and from the award on the action. A hypothetical ten-unit eligible stake counting at twenty-five per cent advances a counter by 2.50 qualifying units if those are the campaign’s rules. The advancement calculation describes the counter, rather than a return or a guaranteed balance change.
The contribution rule can differ between game versions, normal rounds and optional modes. A category label alone may be insufficient. Record the eligible list and any exclusions that belong to the same campaign as the free-spin allocation. This is particularly relevant if the resulting award must be used under conditions different from those governing the original allocated rounds.
When comparing two campaigns, show the requirement and contribution side by side. A smaller requirement with limited contribution is not directly comparable with a larger requirement counting the full eligible stake. The table should explain the inputs rather than invent a universal score. Outcomes and restrictions still need their own treatment, and the counter arithmetic should remain separate from any claim about a session’s financial result.
Understand conversion limits at their own stage
A conversion limit can cap how much resulting promotional value moves into another balance category. It is a different rule from the spin count, stake value or nominal allocation. Identify the point at which the limit is applied and the balance to which it refers. A heading that combines every limit under cashout can hide these distinctions.
For a fictional example, a campaign might define a maximum conversion amount after a requirement is met. An award above that ceiling would not establish that the complete amount converts under those conditions. The comparison should show the credited award, the defined ceiling and the resulting conversion entry separately. The example is an explanation of a possible structure, not a statement about a current brand offer.
A payment route can also have a separate withdrawal limit. That limit does not establish whether the promotional value has already converted. Keep the conversion decision and the withdrawal request as different events. A clear record can show that conversion is confirmed while payment dispatch remains unanswered, or that no conversion entry has yet been established. Each conclusion should follow from its own evidence.
Record expiry from its actual starting event
A spin allocation can expire from activation, crediting, registration or another defined event. A number of days is incomplete without that starting event and the applicable time zone. Record the timestamp shown in the campaign or account rather than assuming that a later reminder email resets the period. The comparison should preserve the event that actually starts the clock.
Daily allocations can have separate deadlines. A package advertised as several days of spins may release components one day at a time, each with its own use window. A combined count can therefore conceal several different expiry events. Record each component’s release and deadline instead of showing only the latest date for the package. This makes the schedule understandable without suggesting that all rounds become available immediately.
Where screens disagree about expiry, identify the exact campaign and the conflicting timestamps. The useful question asks which condition governs the allocation in that account edition. A short deadline should not be used as a reason to assume an unresolved qualification has been satisfied. The purpose of the schedule is to make the conditions clear, not to turn an attractive count into pressure to change a spending plan.
Activation and allocation are separate events
An account can display a promotion before an allocation has been activated or credited. Record the stages shown by the interface rather than treating every promotional tile as an immediately usable balance. An opt-in confirmation, a qualifying-event acknowledgement and an allocation entry can be separate records. The campaign terms should explain how they connect.
If a control reports that an action has been accepted, preserve the actual message and its date. A general acknowledgement may establish submission without establishing final eligibility. Conversely, an allocation entry can provide evidence that the rounds were credited even where a reminder message arrives later. Connecting the events by campaign name makes the chronology easier to interpret.
A precise enquiry describes the missing stage. The campaign was activated, the qualifying event is recorded, but the allocation entry is absent is a different question from the allocation exists but the eligible title will not load. Another account might show a rejected activation with a stated reason. These observations should not all be compressed into one unsupported conclusion that the promotion is broken.
Compare scheduled components one by one
A multi-day or multi-stage package should be represented as a set of components. Each component can have a count, stake value, eligible title, release event and expiry. A single package total may be useful as a summary, but it cannot replace those component terms. Compare the same stage across campaigns before adding totals that depend on later qualifications.
For example, a fictional package could contain an initial allocation and later components released under defined conditions. The complete advertised count would not establish that every component is available after the first event. Show which components are confirmed in the account and which remain conditional. A comparison that treats later components as immediately credited would misdescribe the package even if its total count were copied correctly.
The resulting awards can also need separate records if the components use different games or balance rules. Keep each allocation identifier or date beside its resulting entry. This makes it possible to investigate a missing component without questioning parts already reconciled. It also supports a later correction if the campaign changes: one component can be updated without rewriting the rules of unrelated allocations.
Check any maximum-stake condition on resulting play
A maximum-stake rule attached to a promotional balance needs to be compared with the complete amount committed in the selected mode. A small base figure in a game control can be different from the total after line, denomination or optional-feature settings are included. Record the total in the account currency and connect the condition to the exact campaign that credited the balance.
An allocation’s original fixed spin stake is not necessarily a universal permitted stake for every later action using resulting value. The campaign may define separate rules for those stages. Keep the allocated rounds, resulting credit and later eligible actions distinct. This prevents the original allocation’s appearance from being used as an unsupported interpretation of the entire promotion.
For a disputed action, preserve the round reference, selected mode and applicable condition. A current screen can describe settings different from those used at the time. The enquiry should ask which rule was applied to that particular action and balance. A precise record is more useful than trying to reproduce the event with additional actions, each of which would create another result to explain.
Separate account currency from promotional units
A promotion can display a currency symbol that needs further identification. Australian dollars, New Zealand dollars, Canadian dollars and US dollars are different units even though several use a dollar sign. Record the explicit code where it is available. A nominal allocation calculation should use the stake’s actual unit rather than a guessed currency inferred from the language or flag on a public page.
If a game uses credits, preserve both the credit count and the denomination that connects it to account currency. A different edition may use another denomination. The comparison can then show the original display and the converted nominal amount with its stated rule. It should not replace the campaign’s conversion definition with a market quotation from another date.
Keep external payment conversion separate as well. A bank’s debit amount can reflect its own currency treatment while the promotion uses an account-currency qualification. The bank receipt, account credit and spin allocation therefore need their own values. An unexplained difference between those records should be investigated through the actual transaction and campaign terms rather than treated as an automatic change in the value of each spin.
Understand cancellation at the relevant balance stage
Cancelling or declining a promotion can affect allocated rounds, promotional credit or resulting awards under the actual campaign terms. The effect cannot be inferred from the word cancel alone. Identify the account state before the action and the specific balances the confirmation screen says it will affect. Keep the campaign name with that record.
Declining an unactivated campaign, cancelling an active allocation and withdrawing after a confirmed conversion are different stages. A compact interface may use similar wording around several actions, making the surrounding context especially important. The comparison should preserve the stage instead of applying one general cancellation explanation to every situation.
If an existing balance changes, ask which entry records the movement and which campaign condition governs it. A combined total after several unrelated actions may not show the allocation’s effect clearly. Keep the cancellation entry separate from deposits, game awards and payment requests. This makes it possible to explain the actual movement without inventing a universal rule or assuming that every amount returns to the same category.
Distinguish a game-loading problem from a missing allocation
An allocation can be present while the eligible game fails to load, and a game can load while the allocation is absent. These observations call for different enquiries. Record whether the account shows the allocated rounds, which eligible title is named and what the game interface reports. A general statement that the spins do not work can hide the evidence needed to identify the stage.
For a loading issue, note the device, browser, edition and exact message shown, while avoiding unnecessary private account information. An interface problem is not automatically evidence about the underlying allocation or its expiry. If the service provides a status record for the campaign, keep that record beside the loading message so the two can be assessed separately.
For a missing allocation, identify the activation and qualifying-event records instead. A screenshot of an unrelated playable title will not establish that the campaign’s designated game was eligible. The practical enquiry connects the exact campaign to the absent entry. This distinction also improves comparisons: game availability, interface usability and promotional crediting should not be collapsed into a single unexplained rating.
Worked example: the same count with different stakes
Imagine Allocation A and Allocation B each advertise twenty fictional spins. A defines a stake of 0.10 units per spin, producing two nominal stake units. B defines a stake of 0.50 units, producing ten nominal stake units. The matching spin count therefore describes different nominal allocations. A table showing only twenty in each row would hide a meaningful difference.
That difference still does not identify the resulting awards. The games, configurations and outcomes remain separate. Record the nominal inputs and then describe the actual conditions governing any awards, including balance treatment, requirement, contribution and conversion. A larger nominal allocation is one descriptive fact rather than a guarantee that the eventual value received will be larger.
The comparison conclusion should identify precisely what differs. It can state that the count is the same and the stake per spin is different, while leaving unknown outcomes uncertain. If one campaign’s stake value is missing, the useful conclusion is that its nominal total is unresolved. Choosing the more attractive value from another review would replace a real information gap with an invented allocation.
Worked example: a staged allocation and its remaining count
Imagine a fictional campaign with forty spins at 0.10 units available in the first stage and thirty spins at 0.20 units scheduled for a later stage. The first component represents four nominal stake units and the second represents six. The maximum described package therefore contains seventy spins and ten nominal stake units if both stages are actually issued under the stated conditions. That is a package description, not ten units of guaranteed winnings or an immediately available cash balance.
Now suppose twenty of the first-stage spins have been used while the second stage has not yet been issued. The record should show twenty first-stage spins remaining, representing two nominal stake units. The later thirty spins remain a separate conditional allocation. Adding those future units to an available account balance would mix an issued entitlement with a scheduled component whose conditions still need to be met.
If the first stage expires before the remaining twenty spins are used, record that expiry against the first component. Do not silently transfer its unused nominal value into the second stage. Likewise, a delayed second-stage allocation should be described as an allocation question rather than a missing bank payment. The campaign name, component, expected release event and actual account entry are the useful fields for an enquiry.
The staged comparison therefore needs more than a single total. Preserve the count, stake unit, release condition, issue date, expiry and remaining count for each component. Keep any resulting award in another field because its value is an outcome, not the multiplication used to describe the allocation. This approach can explain a changing package record without inventing a payout, treating a future component as cash or assuming that every advertised spin is currently available.
Worked example: three daily release windows on a timeline
Consider a different fictional campaign with ten spins scheduled on each of three days. Its invented rules release each component at 09:00 and expire it at 08:59 the following day, using a fixed UTC+10 offset. The thirty-spin package is a schedule of three components. It is not a single allocation whose entire count remains valid until the final day's deadline.
At a fictional checkpoint on day two, the reader's record might show eight first-day spins used, the remaining two expired, the second day's allocation unconfirmed and the third day's release not yet due. Those are four different statuses. Describing the entire thirty-spin package as missing would erase the confirmed first-day activity and the future timing of the third component.
The useful enquiry concerns the second component: which release event applied, whether it occurred and which account entry records it. Keep the invented schedule, actual observation time within the example and stated offset together. A notification received at 09:02 is not automatically the release event's recorded time. If a real campaign omits its timezone, ask for that field rather than assigning an Australian city or daylight-saving offset by guesswork.
This calendar example answers a timing question, while the preceding example answers a mixed-stake allocation calculation. The records needed differ. For timing, preserve component dates, release conditions, issue events and expiry. For nominal allocation, preserve each count and stake unit. Both can sit in the same worksheet without turning a scheduled component into currently available cash.
Worked example: awards with a conversion ceiling
Suppose a fictional account record shows eighteen units of promotional value and the applicable invented terms cap conversion at ten units after the documented conditions are met. At the conversion checkpoint, assume the recorded eligible balance is still eighteen units. The conversion is the smaller of eighteen and ten: ten units. The remaining eight units are the difference explained by this fictional ceiling, not a separately completed bank withdrawal.
Keep three values in the worksheet: the pre-conversion eligible balance of eighteen, the cap of ten and the actual conversion entry of ten. Do not rewrite the original award as ten merely to make the final record look simpler. The larger original value and smaller converted value answer different questions. If the actual entry were nine rather than ten, the additional one-unit difference would still need its own explanation; the stated ceiling alone would not explain it.
Now imagine a separate fictional withdrawal request for eight units from the converted balance, with no fee in this example. The account could show two converted units remaining and an eight-unit request under review. That record does not establish that eight units reached a bank. A later dispatch and destination credit would need their own identifiers and amounts before receipt could be described as confirmed.
This example isolates a cap calculation from a payment-stage question. It does not predict an award, assume that playing through a requirement preserves a balance or state real terms for any displayed brand. The eighteen-unit amount is a stipulated checkpoint in a fictional ledger. Its purpose is to show which difference the cap explains and which later movement still requires evidence.
Read a counter movement as its own record
A promotional counter can display progress toward a defined requirement. That progress needs to be understood using the campaign’s eligible-game and contribution rules. The number is not necessarily a cash balance, a round award or a withdrawal amount. Preserve the label and unit shown beside it before interpreting a change.
A round can produce both an award and a counter movement, but those values answer different questions. An eligible stake can advance a requirement regardless of whether its award is larger or smaller than its cost. Combining the award and the counter advancement into one supposed return would mix unrelated measurements. The comparison should identify each quantity and its calculation separately.
When a counter seems inconsistent, record the original and later counter values, the qualifying actions and the relevant contribution condition. A support question can then identify the specific difference. A screenshot of the final counter alone may not show which actions were eligible or when the campaign became active. The useful record connects the change to the campaign and its actual event sequence.
Keep source evidence close to each comparison field
A free-spin comparison is easier to maintain when each condition has a source and check date. An account entry can establish that an allocation was credited, while a campaign page can define its conditions. A review can establish what another publisher reported, but that does not make it an independent account test by this site. The type of evidence belongs beside the claim.
Conflicting sources should be recorded rather than forced into agreement. A review of an older edition can use another stake value or deadline. The current loaded game and the applicable campaign terms may answer the present question differently. Identify the editions and dates before deciding which source is relevant. This keeps a historical description useful without presenting it as a current campaign confirmation.
The comparison should also identify missing evidence. A known spin count with an unknown stake value remains incomplete even when several sites repeat the same count. A precise open question is useful because it identifies what the actual campaign terms need to establish. It is preferable to an apparently complete table that combines incompatible figures from unrelated sources.
Create a compact allocation worksheet
An allocation worksheet connects the campaign with the game and the resulting account events. Start with a separate record for each component, including the count, stake unit, release and expiry. Then add the award and balance entries that actually appear. This preserves the sequence and avoids replacing the original values with a newer promotional screen.
Use clear event labels. Activation, qualification, allocation, round result, credit, conversion and payment request are different records even when the interface presents them near one another. A worksheet does not need every unrelated account movement. It needs enough information to identify which event is established and which event remains unanswered.
A short list of missing fields is a useful part of the worksheet. It can identify an unspecified stake value, an unclear balance label or an absent conversion entry. The next enquiry can then ask for that exact information. This approach helps the reader act on an information gap without turning the comparison into a promise that a particular promotion will produce withdrawable value.
Ask a focused question about a missing component
A useful enquiry identifies the campaign, account edition, activation event and the component that is absent or disputed. If the issue concerns an eligible game, include the title and exact message. If it concerns a resulting award, identify the allocation and round or history entry. The recipient should be able to locate one clear event without reconstructing the whole account from scattered screenshots.
Keep private authentication information out of the enquiry. Use the service’s legitimate channel for any necessary financial or identity documents, and share only material relevant to the question. A public discussion does not need complete account details. Preserve a secure original copy of the evidence so a legitimate clarification can be answered accurately if more context is needed.
When a reply arrives, record which stage it resolves. An acknowledgement of activation does not necessarily establish crediting, and a confirmed credit does not necessarily establish conversion. Keep the remaining question visible in the same chronology. This produces a clearer account than repeatedly opening new conversations that use different descriptions for the same allocation.
Evaluate an advertised spin count within a complete comparison
A useful free-spin comparison gives the count an appropriate place among the other conditions. It shows the eligible game, stake value, schedule, expiry, balance treatment and any requirement or conversion limit. A large count can then be understood as one field in a defined campaign instead of being treated as a complete cash value.
The description can remain readable without hiding the important inputs. A compact summary can state the known count and stake, while a detailed section explains the balance and conversion stages. Where a condition is unresolved, identify it directly and connect it to the exact campaign question. This keeps the page useful even when the public information does not support a fully populated offer table.
The finished record supports later updates as well. If a stake value or campaign schedule changes, the affected component can be corrected without silently changing unrelated entries. The comparison remains anchored to its source and date. Its purpose is a reproducible explanation of an allocation and its conditions, rather than a prediction of the awards from a future sequence of spins.
Example of a readable allocation record
A fictional record can make the field structure easier to follow. Write the campaign name and check date first. Identify Component One, its named game version and its twenty allocated spins at a defined 0.10-unit stake. Record the two-unit nominal input separately from the actual round awards. If the campaign later credits a promotional balance, add that entry with its own identifier and the condition set governing it.
The next line can identify the stage that remains open. For example, the allocation and award entries are present, but the conversion entry has not been established. The support question then asks about conversion under the named campaign rather than asking whether the original spins existed. Another fictional record might instead show the qualifying event but no allocation entry. The worksheet changes with the evidence gap, even when the headline count is the same.
When the missing entry is clarified, add the source and date of the answer. Keep the original allocation inputs so the chronology remains understandable. The record now explains which stage was resolved and which later stages, if any, still need evidence. A reader can follow the calculation and the account sequence without assuming that the nominal allocation was cash, that every award converted, or that a subsequent payment was already received.
Sources and method
Quick answer
How do I calculate the nominal value of free spins?
Multiply the defined spin count by the stated stake per spin using the actual currency or credit conversion. That gives nominal stake inputs, not a forecast of awards or a guaranteed withdrawable amount.
Do identical spin counts mean identical allocations?
No. Stake values, eligible games, schedules and the conditions of resulting awards can differ. Compare the same fields for each exact campaign before treating the allocations as equivalent.
What is the difference between conversion and withdrawal?
Conversion concerns how a promotional amount moves into another balance category under its terms. Withdrawal concerns a later payment request and movement to a destination. Each stage needs its own record.
Which expiry should be used for a multi-day spin package?
Use the release and expiry conditions for each component, including the applicable zone. A final package date does not automatically extend an earlier component’s separate deadline.
What evidence helps when an allocation is missing?
Keep the exact campaign, edition, activation and qualifying-event records, and identify the absent component. For a game or award issue, include the relevant title and history reference rather than unrelated account totals.