About the ARPU Calculator
This calculator finds average revenue per user (ARPU), one of the most common metrics for subscription and app-based businesses: the average dollar amount each user or customer contributes to revenue over a given period. It is built from two inputs, total revenue and total users, so it works whether you are measuring across an entire subscriber base or a specific customer segment. The result gives a single per-user benchmark that is easy to track across periods.
How It Works
Enter total revenue collected during the period and the total number of users or customers over that same period, then the calculator divides revenue by user count to get the average dollar amount attributable to each user.
Formula & Methodology
By hand, this is a single division: add up all revenue recognized during the period from the user base being measured, then divide by however many users are included in that same base for that period. Keeping the numerator and denominator aligned in both scope, which revenue counts and which users count, and time period is what makes the resulting figure trustworthy for period-over-period comparison.
Examples
A paid subscription business
$84,000 in revenue divided across 1,200 paying customers produces an ARPU of $70.00 for the period.
A freemium app counting all active users
$18,000 in revenue divided across 45,000 total active users, including free-tier users who generate no revenue, produces an ARPU of $0.40, far lower than the paying-customer example, since the denominator includes a much larger non-paying base.
Advantages
- Reduces a full period's revenue and user count into a single, trackable per-user figure useful for spotting trends over time.
- Works for both paid-only user bases and freemium models, as long as the user count entered matches the definition being tracked.
- Useful as a quick benchmark when comparing revenue efficiency across products, cohorts, or time periods of different sizes.
Common Mistakes
- Switching between 'paying users' and 'all active users' as the denominator from one period to the next, which makes ARPU trends meaningless even though each individual number is technically correct.
- Treating ARPU as if it applies evenly to every user, when a small number of high-spending accounts can pull the average well above what a typical user actually pays.
- Using a snapshot of user count from a single day rather than a period average, which skews the result when user growth or churn was significant during that period.
Edge Cases to Watch For
- If total users is zero, the calculator returns an error rather than dividing by zero.
- Whether 'total users' means paying customers only or your entire active user base, including free-tier users, makes a large difference in the result, and the calculator does not distinguish between the two, so the definition needs to stay consistent between periods for the trend to mean anything.
- User count is treated as a single figure for the whole period, so if your user base grew or shrank substantially mid-period, using an average of the starting and ending counts gives a more accurate ARPU than using either endpoint alone.
Common Use Cases
- SaaS and subscription businesses tracking revenue efficiency per user across billing periods.
- Freemium and ad-supported apps comparing how monetization changes as the free-user base scales.
- Investors and analysts benchmarking revenue efficiency across companies with different user base sizes.