乗換路線図 vs Uber - Request a ride
Revenue, downloads, ratings and category context for two iOS apps. Figures are estimates and should be read as ranges, not exact totals.
乗換路線図TOKYO STUDIO INC. - Travel
Uber - Request a rideUber Technologies, Inc. - Travel| Metric | 乗換路線図 | Uber - Request a ride | Readout |
|---|---|---|---|
| Estimated revenue / mo | $*** - opens with trial | Not resolved | Partial signal |
| Revenue band | $*** - opens with trial | Not resolved | Use range + confidence |
| Estimated downloads / mo | $*** - opens with trial | ~5.0M | Uber - Request a ride |
| Download band | $*** - opens with trial | 5.0M (point est.) | Use range + confidence |
| Rating | - | 4.90 | Uber - Request a ride |
| Rating count | - | 16.5M | Uber - Request a ride |
| Tracked keywords | — | — | Tie |
| Category | Travel | Travel | Same market |
Which app is bigger?
乗換路線図 and Uber - Request a ride are compared inside Travel with monthly revenue, downloads, rating, review volume, keyword footprint, category placement and range context. Uber - Request a ride leads on monthly downloads in the current readout, while a clean revenue readout is available only for 乗換路線図 in this pair. Uber - Request a ride wins demand, Uber - Request a ride has deeper review volume, and Tie has the larger tracked keyword footprint. The better app depends on the job: choose the revenue leader when you need monetization proof, choose the download leader when reach matters, and choose the higher-rated or deeper-reviewed app when market trust is the constraint. Read both ranges rather than only the midpoint, then open the category hub and related collections to see whether this pair is an outlier or a normal category pattern.