In short
App Store revenue estimates are modeled guesses. In general, a model takes an app's rank on public charts, in a given country and category, and converts it into downloads and revenue. AppHitlist does this with its own algorithm on Apple's public chart lists, updated daily. The results are estimates, not exact numbers, and they can be wrong.
What is an App Store revenue estimate?
An App Store revenue estimate is a calculated guess of how much an app earns. Only the developer sees the real figure, inside App Store Connect. Apple shows the public only rankings, ratings and prices.
So every outside number comes from a model. The model starts from what is visible, mostly chart positions, and works backward to a likely amount of downloads or revenue. How good the answer is depends on how good the model is and how much data it can see.
That is why two services can give different numbers for the same app. Neither one is looking at the real total.
How does chart rank turn into downloads and revenue?
In general, the link between rank and volume is not a straight line. The few apps at the very top of a chart usually get far more downloads or revenue than the apps just below them. Further down, the gap between neighbors gets small, and the curve flattens out.
Models are typically tuned against apps whose real numbers are known, for example data that developers have shared. The model learns roughly how much volume a given rank corresponds to, then applies that to every other app on the chart.
This works better for ranks near the top, where the curve is steep and each position means a lot, than for ranks deep in the list, where a move of ten places can mean very little. A single day can also mislead, so a model that looks at rank over many days usually has a steadier picture than one that looks at a single snapshot.
Why do category and country change the numbers?
Charts are not global. There is a separate chart for each country, and usually one for each category inside it. The same rank can stand for very different volume depending on where it appears.
A top 20 position in a large market generally implies more downloads than the same position in a small market, because the whole audience is bigger. In the same way, a rank in a crowded category such as games can reflect a different volume than the same rank in a smaller category.
Prices and currencies matter too. The same subscription costs different amounts in different countries, so revenue at the same rank is not the same everywhere. A good model keeps charts apart by country and category and does not mix them.
Paid apps, in-app purchases and subscriptions: what changes?
A paid app earns once, at the moment of download. A free app with in-app purchases or a subscription earns over time, and renewals keep adding to revenue long after the first install. A model has to treat these cases differently, because download counts alone say very little about money for the second kind.
Free trials add another wrinkle. A user can install an app and start a trial, and the money only arrives later, if at all. Refunds, family sharing and regional pricing also change what the developer finally keeps.
Finally, check whether a figure is gross or net. Apple keeps a commission on each sale, so what the developer receives is lower than what customers paid. Estimates often describe the amount customers spend, not the amount the developer takes home.
Where do the errors come from?
Every model has blind spots. Knowing them helps you decide how much weight a number deserves. These are the usual sources of error:
- Only a limited number of apps appear on each chart, so small apps are hard to see at all.
- A daily chart is a snapshot. It can miss movement during the day.
- Featuring by Apple, a viral post or a burst of ads can lift an app for a few days and distort the picture.
- Rank says nothing about how many users pay on renewals, cancel or ask for refunds.
- The model was tuned on a limited set of known apps, and your app may not behave like them.
- Pricing, trials and bundles differ between apps in ways a chart cannot show.
How does AppHitlist estimate, and how should you use it?
AppHitlist uses its own algorithm, built on the chart lists Apple publishes publicly on the App Store. The charts are saved every day and the estimates are updated daily. They are estimates, not exact numbers, and the data can be wrong. The interface is focused on the US today, so do not read the figures as worldwide revenue.
Use estimates to compare, not to measure. Ask which of two apps is bigger, whether an app is trending up or down over weeks, and whether a category looks healthy. Treat any single figure as a range of possibilities.
Back it up with other signals: rating counts, how long the app has been on a chart, active Meta ads and complaint themes. When several signals agree, you can trust the picture more than any one number.