Gross Gaming Revenue and Net Gaming Revenue are the two foundational P&L metrics in iGaming. Operators that conflate them confuse their tax base, their bonus accounting, their unit economics, and ultimately their valuation. The distinction is not academic. It decides actual money.
The definitions
Gross Gaming Revenue (GGR). Total amount wagered by players, minus total amount won by players. The "hold" before any other deductions. For a casino: deposits used for wagering, minus withdrawals from winning play, ignoring everything else. For sportsbook: amount staked, minus payouts.
Net Gaming Revenue (NGR). GGR minus bonus costs, payment processing fees, gaming taxes, and operator-side promotional liabilities. Different operators include different items in NGR, which is itself one of the problems.
The structural relationship: GGR is what the player population produced. NGR is what the operator actually has after honouring the obligations that GGR triggered.
Why the gap matters
For two operators with identical GGR, the gap to NGR can range from 15% to 60% of GGR. The drivers:
Gaming tax rate. Some jurisdictions tax on GGR at a fixed rate (UK at 21%, Spain at 20%, many LatAm at 12-15%). Some tax on a tiered GGR scale (Italy ADM up to 25%). Some tax on turnover (older Italian model) or stake (some sportsbook jurisdictions). Tax can be 10% or 40% of GGR depending on jurisdiction.
Bonus cost recognition. Operators that book bonus cost above-the-line (against GGR) report lower NGR but get a more defensible margin picture. Operators that book bonus below-the-line (treating bonuses as a marketing expense) report higher NGR but distort the headline number.
Payment processing. Typically 1.5-4% of GGR depending on payment mix. Crypto-heavy operators run lower. Card-heavy operators in tier-1 markets run higher.
Game-supplier revenue share. The aggregator and game-studio royalties paid out of GGR. Typically 10-15% of GGR.
Where confusion happens
Three common operator-side confusions on GGR vs NGR.
"GGR margin" is meaningless across jurisdictions. A UK operator at 28% GGR/Turnover ratio is not directly comparable to a Curacao operator at the same ratio. The UK operator pays 21% gaming tax on GGR; the Curacao operator pays approximately zero. The NGR/Turnover ratios are different by a factor of two.
Bonus cost vs bonus liability are different items. Bonus cost is what was paid out as bonus wagering credit. Bonus liability is what is still on player balances awaiting wagering completion. The two move at different velocities. Operators that track only one of them produce misleading NGR.
"Adjusted" NGR is an editorial choice. Public operators often report "adjusted NGR" that excludes specific costs the operator views as unusual or non-recurring. The adjustments are not standardised. Comparing one operator's adjusted NGR to another's is unreliable unless the adjustments are reconciled.
The tax base implication
In most regulated jurisdictions, gaming tax is calculated on GGR, not NGR. The operator pays tax on the gross hold before deducting their own costs. This is one of the largest single-line operator costs and is often misunderstood by founders.
The structural consequence: tier-1 regulated markets (UK, Italy, Germany, Spain, France) have materially lower NGR margins than the headline GGR margin suggests, because tax is taken at the GGR stage. Operators planning multi-market expansion need to model NGR in each market, not GGR, to compare like for like.
A worked example: an operator with USD 100M GGR in the UK pays USD 21M in gaming tax, USD 12M in bonus costs, USD 3M in payment fees, USD 12M in game-supplier revenue share. NGR is USD 52M. EBITDA after staff and tech is typically 25-40% of NGR, so EBITDA is USD 13-21M. The same GGR in Curacao produces NGR of approximately USD 85M and EBITDA of USD 30-50M. The same headline number is a different commercial outcome.
The bonus accounting question
The right place to book bonus costs is above the line, deducted from GGR to arrive at NGR. This treatment matches the regulatory reality: bonuses are part of the gaming proposition, not an external marketing spend. Most modern operator accounting follows this convention.
Operators that book bonuses below the line (as marketing expense) overstate NGR. This produces flattering headline numbers but distorts unit economics. The CAC math becomes misleading. The valuation conversation becomes misleading. The internal performance conversation becomes misleading.
The exception worth noting: some bonus mechanics are genuinely marketing (e.g., welcome offers to convert paid traffic). Some are genuinely operational (e.g., loyalty rewards, VIP retention bonuses, reactivation). Sophisticated operators split bonus accounting accordingly: acquisition bonus above marketing, operational bonus above the line. The result is a cleaner picture of where investment is going.
The valuation impact
Public-market and private-market valuation multiples for iGaming operators typically apply to NGR or EBITDA, not GGR. Operators that report inflated NGR (through below-the-line bonus accounting or aggressive adjustments) get lower trust multiples from sophisticated buyers. Operators that report conservatively, with bonus costs above the line, get higher trust multiples.
In sale processes, the buyer's diligence team will pull bonus accounting apart and rebuild NGR with conservative assumptions. The operator that has already done this internally gets to the answer faster. The operator that has not gets surprised. Buyers price the surprise.
The valuation multiple range for a tier-1 regulated iGaming operator at scale is roughly 6-10x EBITDA. The range for an offshore operator with similar GGR is roughly 3-6x. The difference is the trust premium the regulated jurisdiction confers. The internal accounting discipline contributes to where in the range a specific operator lands.
The right way to track both metrics
The operator-side discipline is to track GGR and NGR side by side, with the bridge fully visible. The standard monthly P&L:
GGR
minus gaming tax (line item by jurisdiction)
minus payment processing fees
minus bonus cost above the line
minus game-supplier revenue share
equals NGR
minus marketing (paid acquisition, affiliate commissions)
minus staff and tech
minus general overhead
equals EBITDA
Every line on this bridge is contestable. Every line has accounting choices. The operator that runs the bridge cleanly and consistently makes better decisions than the operator that does not. The buyer in an M&A process is reading the bridge as a signal of operational sophistication.
Where this matters in practice
The GGR/NGR distinction matters most acutely in three operational situations. Multi-market portfolio comparison (different tax rates produce non-comparable GGR margins). Bonus campaign ROI (bonus cost above the line lets you see whether the campaign produced net revenue). Sale or capital raise conversation (the buyer or investor is reading your NGR bridge to assess sophistication and conservatism).
For operators thinking about sale, valuation, or comparative market analysis, the conversation is usually faster on WhatsApp than over a longer engagement. Current GGR/NGR setup, current accounting choices, target outcome. Same-day reply with an honest read on the structural questions.
GGR and NGR: quick answers
What is GGR? GGR (Gross Gaming Revenue) is total player wagers minus total player winnings, before any other deductions. It is the operator’s top-line "hold".
What does GGR mean? Gross Gaming Revenue: the gross win from players before bonuses, taxes and fees. The UK regulatory equivalent is GGY (Gross Gambling Yield).
What is NGR? NGR (Net Gaming Revenue) is GGR after bonuses, free bets, jackpot contributions, payment fees and gaming taxes. It is what actually reaches the operator.
What is the difference between GGR and NGR? GGR is what players produced; NGR is what the operator keeps after the obligations GGR triggers. The gap usually runs 15% to 60% of GGR.
How do you calculate NGR? NGR = GGR minus bonus and free-bet cost, minus gaming tax, minus payment processing fees, minus other promotional or regulatory deductions. Always define the deduction list explicitly when comparing operators.