FREE TOOL
App revenue estimator
An app revenue estimator models how much an app grosses from in-app purchases and subscriptions in a period, using public store signals such as chart positions and rating counts. This tool shows the AppGazers estimate of gross in-app spend for the last full month as an 80% range. It excludes ad revenue, web sales and profit.
What a revenue estimate can and cannot answer
| Question | The estimate can help | The estimate cannot answer |
|---|---|---|
| Market prioritisation | Which comparable apps deserve a closer look | The market’s exact total revenue |
| Relative comparison | Whether modeled ranges differ materially | Which product is more profitable |
| Trend research | Where to inspect a dated change | What caused the change |
| Financial truth | Nothing beyond a labelled hypothesis | Reported proceeds, refunds, store fees or ad revenue |
How to read the result
Each app page shows two numbers: the low (P10) and high (P90) ends of an 80% range for gross in-app spend in the named month. Read the range, not a single figure. A wide range means the public signals for that app support less certainty.
An app below the model’s floor shows “< $5K”. An app the model could not estimate shows “Not estimated”, which means missing, not zero. The figure is worldwide; filtering a store record by country does not make it a country-level estimate.
What an app revenue estimator actually estimates
A third-party estimator models a figure from available signals and assumptions. Treat its output as a modeled range or a comparison input, never as the developer’s reported proceeds. Gross in-app spend is what users pay through the store before Apple’s or Google’s commission, so it is not what the developer receives.
The owner of an app account has a different evidence source: App Store Connect sales reports and Google Play financial reports. Those first-party reports are not available for a competitor’s app through public store pages.
Compare labelled ranges, not false precision
Compare apps on the same store and the same month. If ranges differ by an order of magnitude, the useful conclusion is usually which apps deserve deeper research. Do not add ranges together into a precise market total.
Pair the estimate with observable context: pricing language on the listing, ranking movement, review velocity and public ad creative. Those observations suggest what to investigate; they do not prove what caused a change.
Worked example: a revenue comparison that stays honest
Hypothetical example: three meditation apps show estimated monthly gross in-app spend ranges of roughly $10K–$30K, $80K–$140K and $90K–$150K. The responsible reading is that the first may be a smaller comparable and the other two merit a closer look, not that any developer earned a specific amount or profit.
The next step is to compare their subscription language, recent reviews, ranks and creative. If the hypothesis is that a narrow sleep use case has room for a simpler offer, a landing-page test tests it, not the estimate.
Write an estimation note a teammate can audit
Record the provider, retrieval date, store, period, the range as shown, the comparison set and the decision it informed. Add the limitation: estimates do not include every revenue stream and do not replace first-party reporting.
Frequently asked questions
How accurate is an app revenue estimate?
It is a model, not a measurement. AppGazers shows an 80% range (P10 to P90): the band the model expects the actual figure to fall inside about eight times out of ten. Use it to compare apps and prioritise research, not as a reported number.
Does the estimate include ad revenue?
No. It is modeled gross in-app spend: in-app purchases and subscriptions paid through the App Store or Google Play. It excludes advertising revenue, web sales and profit.
Is the estimate what the developer actually receives?
No. Gross in-app spend is measured before Apple’s or Google’s commission, so the developer’s proceeds are lower. Only the account holder’s App Store Connect or Google Play reports show proceeds.
Which month does the estimate cover?
The last full calendar month the model has run for, which can trail the calendar while a new model run is pending. Every app page names that month, for example “last full month: August 2026”, so you never have to guess the period.
Can I see an app’s revenue by country?
No. The estimate is worldwide for each store listing. AppGazers does not produce country-level revenue estimates.
Do I need an account to use the revenue estimator?
No. The estimator and the app estimate pages are free without signing in. The full AppGazers research workspace is free during beta after Google sign-in.
Official sources
- App Store Connect sales reports — Apple’s first-party reporting documentation for account holders.
- Google Play financial reports — Google’s first-party financial-report documentation for account holders.
GO DEEPER
Estimates, keywords, reviews and ads in one place.
The AppGazers research workspace is free during beta and opens after Google sign-in.
Explore rising apps