THE VERDICT · NOT SUPPORTED
Departures rarely explained most of a big climb.
In the chart events I studied, large climbs usually reflected improved position against apps that stayed in the chart. Once I also counted new arrivals above the climbing app, departures were the main arithmetic explanation in only a small fraction of cases.
That tells me about relative chart position. It does not tell me whether downloads increased or what caused the movement.
See what I found ↓
MY QUESTION
Did the app pass competitors, or did they disappear?
An app can move up a chart for more than one reason. It can pass apps that remain visible, benefit when apps above it leave the top 100, or lose places to new arrivals above it. I wanted to understand which movements mattered in large climbs.
I selected apps that gained at least 10 places between two complete daily charts.
I checked who stayed, who left and who entered above the climbing app.
I compared movement against continuing apps with departures after subtracting new arrivals.
Leaving the top 100 does not mean an app was removed from the store. It could simply have fallen below the chart.
MY THEORY VS THE RESULT
The disappearing competitor story was rarely the main explanation.
My theory
At least one in four large climbs would get at least half its gain from departures after accounting for new arrivals.
What I found
The observed shares were far below that target in both stores and both periods. My original prediction was not supported.
departures − arrivals → net effect
Selected chart events after accounting for arrivals above the app; this does not measure downloads.
See the original result chart
Full sample. A smaller percentage means this explanation was less common in the selected climbs.
One climb is one app in one country between two daily charts. Apps and chart dates can repeat, so these are not 6,819 independent campaigns.
Across the selected climbs, about 92.5% of the gained positions on the App Store and 90.45% on Google Play came from improved standing against apps that remained in the chart. These are shares of positions, not shares of downloads or ASO success.
REAL APPS IN MY SAMPLE
What did the arithmetic look like?
These historical examples were selected after the analysis to explain the result and its exceptions. They are not a random sample, proof of causes or claims of client relationships.
APP STORE · UNITED STATES
Disney+
It moved from 77 to 57. It passed 20 continuing apps. Two apps above it left, but two new arrivals appeared above it, cancelling that part of the gain.
GOOGLE PLAY · UNITED STATES
Indeed Job Search
It climbed from 62 to 40. Its improved standing against continuing apps accounted for 21 of the 22 places gained; departures after arrivals accounted for one.
GOOGLE PLAY · INDIA
Instamart
It climbed from 87 to 77 even though it lost one net place against continuing apps. Departures after arrivals contributed 11 positions. This was an exception, not the typical result.
- 20 places gainedIt passed 20 apps that stayed in the chart.
- 2 departuresTwo apps previously above it left the top 100.
- 2 arrivalsTwo new apps appeared above it, offsetting those departures.
- Result: 20 placesThe gain against continuing apps accounts for the full climb.
THE EXCEPTIONS
Could an app climb without improving its net standing against continuing apps?
Yes. I found three such cases among the 6,819 selected climbs, all on Google Play in the earlier period. Each still passed some continuing apps, but lost as many or more places to others. Entries and exits can matter; these cases do not make them the main explanation for most climbs in my sample.
MY ASO TAKEAWAY
Look at what a chart climb actually means.
My ASO tip: When an app moves up, compare the surrounding chart and check whether it improved against apps that stayed visible.
My ASO strategy: Keep chart movement, search visibility and conversion as separate measures. Investigate a rise over time rather than assigning a cause from one screenshot.
My ASO warning: Passing competitors in a chart does not prove a title change worked or that downloads increased. I did not have the private performance data to test either claim.
WHAT I COULD NOT PROVE
Here is where the evidence stops.
- Why an app moved: I did not measure advertising, listing changes or other causes.
- Downloads: A chart is a relative position, not a download count.
- Search results: I studied broad free app charts, not keyword rankings.
- Every app: The sample uses a short period from one third party collector and excludes incomplete chart pairs.
- Why an app left: Absence from the next top 100 does not reveal whether it fell lower, became unavailable or was affected by collection.
SOURCES & METHODS
Want to check my work?
I used AppOrbit’s archived charts. I reran the supplied verifier to rebuild chart movements and competitor membership from the saved records. It checks the arithmetic against the archive, not the accuracy of the original collector or the cause of movement.
The source evidence and full technical report are kept locally while third party redistribution rights are reviewed.
Read the original report and technical details
ASO Research · Experiment 8Big app-chart climbs usually involve overtaking competitors.
We tested whether apps often climb because competitors disappear from the top 100. Across 6,819 large climbs, that was rarely the main explanation.
Prepared 27 October 2026 · Source observations: 19 September to 26 October 2026, UTC · Apple App Store and Google Play · Top-free app charts
The resultReal app examplesThe exceptionsChecksMeaning for ASOData and method The original theory was not supported as a common explanation.After subtracting new arrivals above an app, departures explained at least half its gain in just 1.33% of Apple climbs and 2.93% of Google Play climbs. Most big ranking gains involved improving position against apps that remained in the chart.
1. What we tested, in plain English
The original idea was simple: your app might jump from #50 to #30 because 20 apps ahead of it leave the top 100. Your ranking improves, but you have not passed any of the competitors that remain.
That was a hypothetical example. We checked how often something similar actually happened, using apps that climbed at least 10 positions between consecutive daily charts. Both charts had to contain a complete, valid top 100 and be recorded 18 to 30 hours apart.
There is one important adjustment. If apps leave from above you but other apps enter above you, those arrivals take positions back. We therefore count departures above the app minus new arrivals above it. We then ask whether that balance explains at least half of the climb.
| Store | Large climbs | Distinct app IDs | Climbs at least half explained by entries/exits | Share of climbs | Departure-only share, before subtracting arrivals |
|---|---|---|---|---|---|
| Apple App Store | 3,988 | 837 | 53 | 1.33% | 6.64% |
| Google Play | 2,831 | 806 | 83 | 2.93% | 7.59% |
One climb means one app, in one country, over one daily chart pair. The same app can appear on several dates or in several countries. These are 6,819 ranking events across 1,643 store-specific app IDs, not 6,819 independent ASO campaigns. The last column retains the original departure-only calculation so the adjustment is transparent.
Even before subtracting new arrivals, the departure-only figure was just 6.64% for Apple and 7.59% for Google Play. The result does not depend on introducing the stricter adjustment.
2. Where the gained positions came from
For each climb, we separated movement against continuing competitors from the balance of apps entering and leaving above it.
| Store | Average positions gained | From passing continuing competitors, after losses | From departures minus new arrivals | Share of all gained positions from continuing competitors |
|---|---|---|---|---|
| Apple App Store | 20.57 | 19.02 | 1.54 | 92.50% |
| Google Play | 18.72 | 16.93 | 1.79 | 90.45% |
On Apple, a large climb averaged about 20.6 positions. Roughly 19.0 came from improved standing against apps still in the chart, and 1.5 from departures minus arrivals. Google Play showed the same broad pattern.
The final column divides the total contribution from continuing competitors by all positions gained in the selected climbs. It is a share of chart positions, not a share of downloads, users or ASO success. Displayed averages are rounded.
3. A real example: Disney+ climbed 20 places
On Apple’s US chart, Disney+ moved from #77 to #57 between 10 and 11 October.
| What changed? | Effect on Disney+’s position |
|---|---|
| It passed 20 apps that stayed in the chart | +20 |
| Two previously higher apps left the top 100 | +2 |
| No previously lower continuing apps passed it | 0 |
| Two new chart arrivals appeared above it | −2 |
| Total movement | +20 positions |
The two departures helped, but the two arrivals cancelled that help. The full 20-position gain remained when we compared Disney+ only with apps visible on both days.
This is evidence of improved relative chart position. It does not tell us why Disney+ improved or whether an ASO change contributed.
Four real climbs, with very different explanations
| App | Store, country and end date | Chart movement | Net gain against continuing apps | Departures minus arrivals | Total gain |
|---|---|---|---|---|---|
| Disney+ | Apple App Store · US · 2026-10-11 | #77 → #57 | 20 | 0 | 20 |
| Indeed Job Search | Google Play · US · 2026-10-08 | #62 → #40 | 21 | 1 | 22 |
| eBay: kaufen & verkaufen | Apple App Store · DE · 2026-10-19 | #99 → #84 | 5 | 10 | 15 |
| Instamart: Groceries & more | Google Play · IN · 2026-09-29 | #87 → #77 | -1 | 11 | 10 |
Indeed’s US Google Play climb was mostly movement against continuing competitors: 21 of its 22 gained positions. eBay’s German Apple climb was an exception: departures minus arrivals accounted for 10 of its 15 positions.
Examples were selected after the analysis to explain the arithmetic and show exceptions. They are not a random sample. Full timestamps, app IDs, source snapshot IDs and the identity of every contributing competitor are included in the evidence.
4. The strongest version of the theory did happen, but only three times
Across all 6,819 large climbs, we found three where an app gained positions overall while making no net improvement against competitors that remained in the chart. All three were on Google Play in the earlier period.
| App | Country and end date | Overall climb | Net change against continuing apps | Departures minus arrivals |
|---|---|---|---|---|
| GPS Map Camera : Geo Tagging | IN · 2026-09-29 | #83 → #69 (+14) | 0 | 14 |
| Instamart: Groceries & more | IN · 2026-09-29 | #87 → #77 (+10) | -1 | 11 |
| GO / Taxi app for Japan visit | JP · 2026-10-03 | #71 → #61 (+10) | -1 | 11 |
In India, it climbed from #87 to #77 on 29 September. It passed four continuing competitors but was passed by five others, a net loss of one position against that group. Seventeen previously higher apps left the chart, while six new arrivals appeared above it. The arithmetic was 4 + 17 − 5 − 6 = 10 positions gained.
Even these three cases included some direct overtakes. We found no qualifying climb where the app passed zero continuing competitors. The initial hypothetical example therefore did not occur literally in this sample.
These exceptions show that chart entries and exits can matter. They do not support treating most large ranking gains as a result of disappearing competitors.
5. The result repeated in the later period
| Store | Event end dates | Climbs at least half explained by entries/exits | Share | 95% interval, apps resampled | 95% interval, date blocks resampled |
|---|---|---|---|---|---|
| Apple App Store | 20 Sep to 7 Oct | 35 / 1,976 | 1.77% | 1.21% to 2.40% | 0.92% to 2.70% |
| Apple App Store | 8 to 26 Oct | 18 / 2,012 | 0.89% | 0.53% to 1.33% | 0.42% to 1.35% |
| Google Play | 20 Sep to 7 Oct | 54 / 1,460 | 3.70% | 2.75% to 4.69% | 1.96% to 5.55% |
| Google Play | 8 to 26 Oct | 29 / 1,371 | 2.12% | 1.42% to 2.88% | 0.38% to 4.02% |
In the later period, the share fell to 0.89% on Apple and 2.12% on Google Play. The second uncertainty estimate resamples groups of neighbouring dates, since the same chart change can affect many apps at once.
These intervals describe variation within the observed sample. They do not cover every possible collector error or establish how all apps behave. The date split repeats the test within an already-used dataset; it is not a new external sample.
Changing the rules did not rescue the theory
| Later-period check | Apple: qualifying cases / climbs | Google Play: qualifying cases / climbs |
|---|---|---|
| Charts recorded 22 to 26 hours apart | 18 / 1,926 (0.93%) | 29 / 1,279 (2.27%) |
| Climbs of at least 20 positions | 0 / 779 (0.00%) | 0 / 426 (0.00%) |
| App started inside the top 50 | 0 / 501 (0.00%) | 0 / 270 (0.00%) |
| First climb per app in the period | 6 / 629 (0.95%) | 12 / 574 (2.09%) |
| Exclude charts with over 20 departures | 18 / 2,012 (0.89%) | 29 / 1,361 (2.13%) |
| Use each country’s local date | 18 / 2,261 (0.80%) | 43 / 1,661 (2.59%) |
For climbs of 20 positions or more in the later period, there were zero cases where entries and exits explained at least half the gain: 0 of 779 Apple climbs and 0 of 426 Google Play climbs.
This zero is specific to that later sample. In the earlier period, there were 7 such Apple cases and 23 Google Play cases. It is not evidence that the pattern never happens.
Giving each app equal weight instead of each event also left the later result small: 0.81% on Apple and 2.43% on Google Play.
Country-by-country results
Later-period climbs where entries and exits explain at least half the gain. Country samples vary in size. These rows share some apps and dates, so they are not independent studies.
| Country | Apple cases / climbs | Google Play cases / climbs |
|---|---|---|
| Brazil | 1 / 187 (0.53%) | 3 / 150 (2.00%) |
| China | 1 / 168 (0.60%) | No eligible data |
| Germany | 8 / 287 (2.79%) | 0 / 189 (0.00%) |
| United Kingdom | 0 / 240 (0.00%) | 10 / 174 (5.75%) |
| Indonesia | 1 / 102 (0.98%) | 2 / 122 (1.64%) |
| India | 1 / 245 (0.41%) | 5 / 137 (3.65%) |
| Japan | 3 / 258 (1.16%) | 0 / 151 (0.00%) |
| South Korea | 3 / 234 (1.28%) | 4 / 176 (2.27%) |
| United States | 0 / 174 (0.00%) | 1 / 131 (0.76%) |
| Vietnam | 0 / 117 (0.00%) | 4 / 141 (2.84%) |
6. What this means for ASO
A large chart climb usually represented improved standing against continuing competitors in this sample. Dismissing those gains as mostly the result of competitors disappearing would have been wrong.
The finding is about the meaning of a ranking change. It does not prove that the app gained downloads or that ASO caused the improvement. We did not have keyword impressions, listing conversion, download counts, advertising exposure or a controlled ASO test for these apps.
| What the evidence supports | What it does not establish |
|---|---|
| “Disney+ passed continuing competitors during this chart climb.” | “A keyword change caused Disney+ to gain downloads.” |
| “Entries and exits were the main arithmetic contribution in this Instamart example.” | “Instamart did no marketing or experienced no change in demand.” |
| “Most 10-position climbs in this dataset were not mainly entry/exit effects.” | “Every big ranking improvement is a successful ASO campaign.” |
These are top-free app charts. They are not keyword search results. The conclusion should not be presented as a finding about keyword-ranking gains.
7. Method, prediction and verification
- Validate the chart source. We used 714 source snapshots marked valid and complete for the top-free, all-apps chart. We independently checked that every snapshot had 100 unique app IDs and the ranks 1 through 100. All 714 passed.
- Build comparable daily charts. Select the latest eligible chart for each store, country and UTC date. This produced 671 daily charts. Of these, 57 had no chart on the preceding calendar date and 18 more failed the 18-to-30-hour timing rule. The remaining 596 daily chart pairs formed the sample.
- Track apps visible at both ends. There were 54,973 app comparisons. We checked the ranking identity for every one, then selected the 6,819 gains of at least 10 positions. Apps entering from outside the top 100 were not assigned an invented starting rank.
- Separate four types of movement. Add continuing competitors passed and previously higher apps that departed. Subtract continuing competitors that passed the focal app and new arrivals above it. These four quantities exactly reproduce the rank change.
- Repeat and vary the test. Analyse the stores and time periods separately; tighten timing; increase the required gain; restrict starting ranks; keep only one climb per app per period; exclude the largest chart turnovers; and use local dates.
The original prediction and why it failed
The protocol was written before calculating Experiment 8 outcomes. It defined a substantial prevalence as at least one in four large climbs being at least half explained by departures minus arrivals, in both stores and both periods, with at least 30 events per store-period.
That prediction failed in all four store-period groups. The observed shares ranged from 0.89% to 3.70%, far below 25%. The original departure-only measure was also small. The report’s headline describes what we found after testing; it is not a claim that we predicted the opposite result in advance.
This was a written analysis protocol, not an external preregistration. We had already used this source for other studies. No thresholds were changed after seeing Experiment 8 results.
Protocol SHA256: fc9cf43e0ed31c9ea5a5954907d2177788aa769738397e0ea2c0d1b0f41c886e
How the calculations were checked
A separate verification program rebuilt the analysis from the raw chart-entry file. Instead of relying only on the four-component calculation, it removed apps not visible on both days, recalculated positions within the remaining apps, and measured the change in that restricted ranking.
That independently calculated change matched the net contribution from continuing competitors. The verifier rebuilt all 6,819 primary events and all 7,869 local-date sensitivity events, checked every competitor membership list, checked 42 summary cells and reproduced all six app-cluster confidence intervals. All checks passed.
App intervals use 5,000 bootstrap resamples of app IDs, retaining each selected app’s events together. Date intervals separately use 5,000 circular blocks of three consecutive calendar dates. These are two views of dependence, not a joint confidence interval correcting every source of dependence.
One departure can help many apps. In the full sample, qualifying cases were spread over 28 Apple chart pairs and 30 Google Play chart pairs. The five chart pairs with the most qualifying cases contributed 25 of 53 Apple cases and 40 of 83 Google Play cases. We report event totals without pretending those are independent editing decisions.
What the data cannot settle
- A departure is an observed absence from the next top 100. The app might have fallen below #100, become unavailable, or been affected by a collection issue. We do not know which.
- The accounting is descriptive. Removing apps from a calculation is not a real-world experiment in which those apps vanished and everything else stayed fixed.
- The sample is limited. It covers one third-party collector, 38 UTC dates and the markets observed in that source. It excludes incomplete charts and large gaps. Selection can affect the result.
- Overtaking does not prove download growth. Relative position cannot tell us whether the focal app’s downloads rose, fell or stayed flat. Apple documents impressions, downloads and conversion as separately measured metrics; this study does not contain those private performance measures.
- There is no ASO attribution. We cannot assign movement to keywords, screenshots, ratings, advertising or other causes from this chart data alone.
8. Download the evidence
The report includes a downloadable evidence ZIP with the source chart entries, snapshot index, metadata used for names, full event tables, competitor IDs, protocol, analysis code, verification code and results.
Evidence ZIP: 10.2 MB. The ZIP is embedded in this HTML. Python and NumPy are required to rerun the calculations. No images or external scripts are required to read the report.
- AppOrbit pinned dataset
Previously preserved chart entries, snapshot index, metadata extract, format and license. Metadata supplies names only; all ranking calculations use chart records. - Apple: Analytics metric definitions
Context for the distinction between chart position and directly measured impressions, downloads and conversion. These private metrics were not available for this study.
Publication finding: Across 6,819 large daily app-chart climbs, competitors leaving the top 100 were rarely the main explanation once new arrivals were counted. Most climbs reflected improved relative standing against apps that remained visible. That makes the ranking gain meaningful as a relative position change, while leaving its cause and download impact unresolved.
Prepared for Gabriel Machuret · ASO Experiment 8 · Source attribution: AppOrbit. Database rights under ODbL 1.0; third-party store content has separate rights. Analysis dates are UTC unless stated otherwise.
Keep exploring
All ASO experiments · See my chart history study · Track keyword rankings · Choose useful ASO metrics