New data from Garmin, Strava, and Zwift finally shows how far the typical cyclist actually rides. What that number tells you about your own training is not what you think.
If you have ever finished a ride, opened your app, and silently wondered whether your distance was normal, you are not alone.
Comparison is the unofficial sport of cycling. We compare segments, speeds, watts, and now, increasingly, total miles.
So when the three biggest ride-tracking platforms on the planet released their annual numbers, every cyclist with a Garmin on their wrist had the same question. Am I riding more, or less, than everyone else?
The answer is weirder, and more useful, than the per-ride number suggests.
The three datasets do not agree, and the gap is wider than you might expect. Each platform measures a different slice of the cycling population, and that explains almost everything.
Garmin's 2025 cycling data report puts the average cycling activity at 28.6 miles (46 km) lasting 1 hour 55 minutes, with an average speed of 14.89 mph (24 kph).
Most of these rides are logged on Sundays. That is the giveaway.
Garmin's users skew toward dedicated cyclists, the kind who clip in for a weekend century build, not a five-mile commute. The number is high because the audience is committed.
Strava is the largest of the three, with a claimed 195 million users, and its average ride distance is much shorter at 12.8 miles (20.6 km) in 1 hour 4 minutes.
The average speed drops too, to 11.86 mph (19.1 kph).
The likely reason is that Strava captures everything: long road rides, mountain bike loops, gravel grinds, and a flood of bike commutes. Mix in shorter utility trips and the average compresses.
Indoor riders punch above their weight. The average Zwift ride is 16.8 miles (27 km) in just 55 minutes, which works out to 18.33 mph (29.5 kph).
That is not because Zwifters are inherently faster.
Zwift defaults hill gradients to 50% of real-world steepness, removes headwinds, and is built for short, hard interval sessions and races. Speed is structural, not just earned.
If you want the full backstory on how Strava and Garmin compete for your data, the recent Strava lawsuit over heatmaps and segments is worth a read. Their fight is also a fight over the numbers you see every day.
Average it across all three platforms and you get 19.4 miles (31.2 km) in 1 hour 18 minutes at 15 mph (24.1 kph).
It is a clean, satisfying number. It is also, honestly, not very useful.
A 50-mile Sunday ride and a 3-mile coffee shop loop average out to 26.5 miles, but nobody actually rides 26.5 miles twice. Most cyclists live near one of two poles.
One pole is a stack of short utility rides. The other is one big weekly ride padded with a couple of midweek sessions.
The average flatters everyone in the middle and describes almost no one.
How far you ride is mostly a function of when you can ride, not how strong you are.
A parent with two kids and a 9 to 5 will ride differently than a retired roadie in Tucson, even at the same VO2 max.
Compare yourself to a global average and you are really comparing your calendar to a stranger's calendar. That is a fight you cannot win.
Here is the part the platform reports leave out. Distance is not what your body responds to.
Weekly volume at the right intensity is.
A peer-reviewed dose-response meta-analysis published in 2021 pooled data from 17 cycling studies covering 478,847 participants and 27,860 mortality cases.
The headline finding: the optimal weekly cycling dose for cardiovascular mortality reduction is roughly 15 MET-hours per week, which works out to about 130 minutes of moderate cycling.
That is just over two hours a week.
Total. Not per ride.
130 minutes a week is a single Garmin Sunday (115 minutes) plus one 15-minute spin to the cafe. Or two Strava commutes stacked with one longer weekend loop.
It says nothing about whether each of those rides was 8 miles or 28.
For health, the metric that matters is the sum of your weekly minutes inside a productive intensity zone, not the length of any single trip. For performance, the same logic applies, just with bigger weekly totals.
The averages are not useless. They are useful for one specific thing: pacing your own progression.
If you are riding 8 miles per session twice a week and want to train for a century, you do not need to suddenly jump to 28 miles because Garmin says that is normal.
You need a structured ramp. A safe weekly mileage increase of around 10% is the long-standing endurance rule of thumb, and it works for the same reason it works in running.
Plenty of riders go from short midweek loops to 100-mile rides inside a season by following exactly that.
Riding 130 minutes one week and zero the next does not give you the benefit of 130 minutes a week. Consistency compounds, single big efforts do not.
This is the part most cyclists underestimate, and it is why our guide on 16 long-distance cycling tips leads with progression and pacing before it ever mentions a specific distance.
The Garmin, Strava, and Zwift numbers ignore the silent majority of cyclists.
Anyone riding a bike share, a non-connected commuter, or a flat-pedal pub crawl is invisible to these platforms. The data is from the measuring class, which is already a fitness-leaning subset.
If you compared the platform averages to actual transport survey data from cycling-heavy cities like Amsterdam or Copenhagen, the daily-trip distance would crater. Most real-world cycling is short, slow, and utterly unrecorded.
Treat the 19.4 mile average for what it is: the average ride of someone who already owns a bike computer.
Three quiet shifts, none of which involve adding mileage for the sake of it.
First, swap your goal metric. Track weekly time on the bike in productive zones, not per-ride distance. Aim for 150 minutes a week to start, which lines up with both the cycling meta-analysis findings and the World Health Organization's general physical activity guidance.
Second, count consistency, not heroics. Four 30-minute rides will outperform one heroic 120-minute ride for almost every health and fitness outcome. The platform averages bury this because they only report per-activity numbers.
Third, stop comparing. Your Strava feed is full of selection bias: the people who ride a lot post a lot. You are not seeing the riders who quietly hit their weekly minutes and skip the upload.
The headline number from the platforms is 19.4 miles, and you can safely ignore it.
What replaces it is duller, less tweetable, and far more honest: a weekly minutes total, ridden at an intensity that actually moves the needle, repeated for months.
That is the metric that builds endurance, drops your resting heart rate, and adds years to your life.
It will never trend on Strava. But it is the only one your body keeps score of.
Perfect for the new riders!
No spam. Cancel anytime.
