The Math Behind Wagering Requirements: Formulas, Worked Examples and Edge Cases

If you have ever read the terms attached to a promotional bonus, you have probably met a sentence like "the bonus must be wagered 30x before withdrawal." It looks simple. It is not. Behind that one line sit several hidden variables: what the multiplier applies to, how different games contribute, what the maximum stake is, and how long you have. In Turkish the concept is called çevrim, literally "turnover" or "cycle", and it is one of the most misunderstood numbers in consumer-facing promotions.

This article is not about where to play or which offer to take. It is a technical look at the arithmetic, written for developers, analysts and anyone who wants to model these rules correctly. We will derive the core formulas, walk through worked examples, and then spend most of our time on the edge cases that break naive implementations.

Why this is worth modeling carefully

A wagering requirement is a constraint on turnover, not on profit. That distinction is the root of most confusion. A user who reads "30x" often imagines needing to win 30 times the bonus. In reality they need to place bets totaling a certain amount, regardless of outcome. Because every bet carries a negative expected value for the player (the house edge), the more turnover a rule demands, the more of the bonus is expected to be consumed before it can be withdrawn.

Getting this right matters for two reasons. First, any tool that reports a wrong number misleads its users. Second, the expected-cost view is the most honest way to show people that a "free" bonus has a price. If you want to play with a working implementation while reading, the bonus wagering calculator on bahisbonusu.com implements the same formulas described here.

Core definitions

Let us fix notation:

• D = deposit amount
• B = bonus amount
• m = wagering multiplier (e.g. 30)
• c = game contribution rate (0 to 1; slots are often 1.0, table games 0.1 to 0.2)
• e = house edge of the game (e.g. 0.04 for a slot with 96% RTP)
• s_max = maximum allowed stake per bet while the bonus is active
• T = required turnover (the number we want)

If a term like RTP, contribution or max bet is unfamiliar, the bahisbonusu.com glossary (sözlük) has short definitions of each.

Formula 1: bonus-only requirement

The most common structure applies the multiplier to the bonus only:

T = B * m

Example: a 100 unit bonus with a 30x requirement.

T = 100 * 30 = 3,000 units of turnover

Formula 2: deposit plus bonus

Some terms apply the multiplier to deposit plus bonus. This is far more demanding and is a frequent source of surprise:

T = (D + B) * m

Same 30x, with a 100 deposit and 100 bonus:

T = (100 + 100) * 30 = 6,000 units

The headline multiplier is identical; the work required is doubled. Any calculator must expose this as an explicit input rather than assuming one base.

Formula 3: adjusting for game contribution

When a game counts only partially, each unit staked clears only c units of requirement. The real amount you must stake is:

T_effective = T / c

With the 3,000 requirement and a table game contributing 10%:

T_effective = 3,000 / 0.10 = 30,000 units staked

That is ten times the work for the same bonus. When a user mixes games, the cleared amount is a weighted sum:

cleared = sum(stake_i * c_i)

and the requirement is met when cleared >= T.

Formula 4: expected cost

This is the most useful number for a reader, and the one most tools leave out. The expected loss from staking T_effective at house edge e is:

expected_loss = T_effective * e

And the expected value of the bonus once cleared (ignoring caps and variance) is:

EV = B - expected_loss

Worked example, bonus-only, slot at 96% RTP (e = 0.04), full contribution:

T = 100 * 30 = 3,000
expected_loss = 3,000 * 0.04 = 120
EV = 100 - 120 = -20

The bonus is expected to cost more than it gives. Lower the multiplier to 20x and the picture changes:

T = 2,000
expected_loss = 80
EV = 100 - 80 = +20

This break-even analysis is clean: EV is zero when m = 1 / (e / c), i.e. m_break_even = c / e. For a 4% edge and full contribution, any multiplier above 25x has negative expected value on the bonus alone. Showing users this threshold is far more informative than the raw multiplier.

Formula 5: number of bets and time

Given a typical stake s (bounded by s_max), the number of bets needed is:

n = ceil(T_effective / s)

With 3,000 turnover at 2 units per bet, that is 1,500 bets. If the offer expires in 7 days, the user needs roughly 215 bets per day. A tool that surfaces this makes the time dimension visible, which is valuable for anyone trying to keep play within limits.

Worked example: putting it together

Inputs:

• Deposit 200, bonus 200 (100% match)
• 35x on deposit plus bonus
• Slot with RTP 96.5% (e = 0.035), contribution 100%
• Max stake 5, user plans 2 per bet
• 14-day validity

Calculation:

T            = (200 + 200) * 35  = 14,000
T_effective  = 14,000 / 1.0      = 14,000
expected_loss= 14,000 * 0.035    = 490
EV           = 200 - 490         = -290
bets         = ceil(14,000 / 2)  = 7,000
bets per day = 7,000 / 14        = 500

The honest summary: about 14,000 units of turnover, an expected cost of roughly 490, and 500 bets a day for two weeks. Expressed that way, very few people would call it "free money."

Edge cases that break naive implementations

1. Ambiguous base

As shown above, "30x" means nothing without its base. Never default silently. Force the user to choose "bonus only" or "deposit + bonus," or show both results side by side.

2. Zero or missing contribution

Some games contribute 0%. Dividing by c = 0 yields infinity. Your code must treat this as "cannot be cleared with this game" rather than returning Infinity or crashing.

3. Contribution above 100%

Rare, but some terms advertise boosted contribution. Validate the range and decide explicitly whether values above 1 are allowed.

4. Max-bet rule

If the user's planned stake exceeds s_max, many terms void the bonus entirely. A calculator should warn loudly rather than just clamp the value.

5. Max cashout caps

Some bonuses cap winnings that can be withdrawn (for example 5x the bonus). This truncates the right tail of the outcome distribution and makes EV worse than the simple formula suggests. A precise model needs simulation; a simple tool should at least display the cap.

6. Sticky vs non-sticky bonuses

With a "sticky" bonus, the bonus amount itself is removed at withdrawal. In that case the EV formula changes: the user keeps only winnings above the bonus. With "non-sticky" structures, real money is played first and the bonus only activates if it is lost. These are different products and should be modeled separately.

7. Sports bets and minimum odds

For sports offers, terms often require minimum odds (e.g. 1.50) for a bet to count. Bets below the threshold contribute 0. Combination bets may count differently than singles. The house edge is not a fixed RTP but depends on the bookmaker margin, which you can estimate from the implied probabilities of a market:

margin = sum(1 / odds_i) - 1

8. Rounding and currency

Use integer minor units (cents/kuruş) internally to avoid floating-point drift, and round up the required bets, never down. Reporting 1,499 bets when 1,500 are needed is a bug users will notice.

9. Partial progress

Real users are mid-way through a requirement. A good tool accepts "already wagered" and computes the remainder: remaining = max(0, T - cleared).

10. Variance is not captured by EV

EV tells you the average outcome, not the likely one. Over a large turnover on a high-volatility game, many users will bust the balance long before completion. If you want to show that, a Monte Carlo simulation of a few thousand sessions is the right tool, but even a plain sentence explaining that the average hides wide swings is a big improvement.

Summary table

Quantity            Formula
------------------  ------------------------------------
Required turnover   T = base * m (base = B or D + B)
Effective stake     T_eff = T / c
Expected loss       L = T_eff * e
Bonus EV            EV = B - L
Break-even mult.    m* = c / e (bonus-only base)
Bets needed         n = ceil(T_eff / s)
Remaining           max(0, T - sum(stake_i * c_i))

Closing thoughts

Wagering requirements are a small piece of arithmetic wrapped in a lot of terminology. Modeling them correctly is mostly about refusing to hide variables: state the base, apply contribution, show the expected cost and make the time dimension explicit. A tool that does this treats its users as adults who deserve the full picture.

If you want to check the numbers from this article, try them in the çevrim calculator, and look up any term you are unsure about in the glossary. And remember: these products are for adults 18+ only, and no calculation turns a negative-expectation activity into income.