App revenue estimates
An estimated monthly revenue range for 62,455 apps in the catalogue, in 49 storefronts. Always a range, never a single figure, and always labelled as an estimate.
| App | Launched | Est. revenue / mo |
|---|---|---|
| Instant Cash Advance - Zora | 2026-06-09 | $303K–$613K |
| Sprite Catch | 2026-07-22 | $71K–$129K |
| Knock Out : Physics Puzzle | 2026-06-30 | $59K–$107K |
What is estimated, and what is observed
Four things on an app profile are observed facts, read from the App Store: the price, the rating count, the category, and the release date in that storefront. Rankings are observed too — a position on a page, on a date.
Downloads and revenue are estimates, and ASOsight labels them Estimated everywhere they appear. They are shown as a range with a confidence band written in words — High, Moderate or Early estimate — rather than a percentage, because a percentage on an estimate invites a precision that is not there.
No estimate is ever displayed as a point figure. If you see "$8.5K–$15.3K", that is deliberate: the honest answer to "what does this app earn" is an interval.
How the estimate is built
Downloads come first. An app's rating count is public and its accumulation over time is observable, so ASOsight derives a download range from rating volume and the rate at which it changes, calibrated per category — people rate a game at a different rate than they rate a banking app.
Revenue is downloads multiplied by an estimated spend per download, chosen by how the app makes money. A paid app is nearly its price. A subscription app is priced from its subscription tier, plus a standing-base term for subscribers who signed up in earlier months, because monthly revenue depends on who is paying today rather than on this month's installs alone.
A free app with no purchase offer earns nothing on the store, and is estimated at zero rather than at a category average. Getting this wrong in the other direction is the single most common failure of revenue estimates.
Where the estimate is deliberately conservative
Two categories are treated specially because their revenue mostly does not pass through Apple. Retail and food-delivery apps sell physical goods, which Apple's own rules forbid from in-app purchase, so their App Store revenue is a fraction of their business — estimating them from download volume produces figures that are wrong by an order of magnitude.
Free games with no visible purchase offer are treated as advertising-funded rather than as in-app-purchase apps, at a far lower revenue per download.
Both corrections move estimates down, not up. Where a signal is ambiguous, ASOsight prefers to understate.
What you can do with it
Compare what apps in a category actually earn before committing to build in it. Judge whether a competitor's visible success is a large business or a small one. Read a new launch's revenue alongside its download estimate and its keyword footprint on one page — every app profile carries all three, across 62,543 apps.
App Store Connect is not required. These estimates are derived from public data, which is what makes them work for apps you do not own.
The methodology page states the model in more detail, including what each provenance label means and how confidence is banded.
Questions people ask
How accurate are app revenue estimates?
No public tool can be exact, because Apple does not publish per-app revenue. ASOsight states an interval instead of a number and attaches a confidence band — High, Moderate or Early estimate — reflecting how much observed data sits behind that particular app. An app with years of rating history estimates far better than one that launched last week.
How does ASOsight estimate app revenue?
A download range is derived from the app's public rating count and how quickly it is accumulating, calibrated per category. That range is multiplied by an estimated spend per download chosen from how the app monetises — paid price, subscription tier, in-app purchase or advertising. Subscription apps add a term for existing subscribers from earlier months.
Do I need App Store Connect to see revenue estimates?
No. Estimates are built from public App Store data, so they are available for any app in the catalogue including competitors. Connecting App Store Connect adds your own measured figures for apps you own; it does not change the estimates shown for anyone else.
Why is the revenue shown as a range instead of a number?
Because the underlying quantity is uncertain and a single figure would hide that. ASOsight shows an interval with a stated confidence band, and never persists or displays a point estimate as though it were a measurement.
How many apps have revenue estimates?
62,455 of the 62,543 apps in the catalogue currently carry a revenue estimate, across 49 storefronts.
Are revenue estimates available for free apps?
Yes. A free app is estimated from its purchase or subscription offer where one exists. A free app with no purchase offer at all is estimated at zero App Store revenue rather than at a category average, because that is the honest answer.
Why are some big retail apps estimated so low?
Because their revenue does not go through the App Store. Apple's rules forbid selling physical goods through in-app purchase, so a retailer's or a food-delivery service's App Store revenue is a small fraction of its actual business. ASOsight estimates those categories from advertising-scale figures rather than from download volume, which understates the business but describes the store correctly.