How many km on a trainer in a year? My 2,294 km and 87 h

Strava shows me 4,320 km and 137 activities for this year (as of 10 November), all in one pile. I wanted to know how much of that I rode at home, on the trainer. So I counted: from late April to 10 November it was 77 rides, 87 hours and about 2,294 km. That is almost half the time I spent on the bike this year. Since September I have ridden almost only indoors, and October was my strongest month of the whole year. Below are all the numbers, month by month, and what I learned from them. If you are wondering whether a trainer is worth it, this one is for you.

How many km on a trainer in a year? My 2,294 km and 87 h
2,294 km
on the trainer with WattLog.pro in 2026: 2,034 km stored across 64 rides, plus an estimated 260 km for 13 spring rides with no stored distance. Outdoors over the same period: 1,880 km.
77 rideson the trainer, 24 Apr to 10 Nov
87 hof pedalling, no descents, no traffic lights
68 minwas the average ride
163 → 193 WFTP from the Ramp Test, June → October

The year in numbers: trainer vs outdoors

On Strava, all my rides, the trainer ones included, end up in a single summary. That is why in November I added a Volume card to the app (Progress → Form). It splits rides into two groups: the ones ridden on the trainer with WattLog.pro, and the imported ones, which for me means outdoor rides from Strava and files from my bike computer. For my season it looks like this:

Trainer (WattLog.pro)Outdoors
Rides7769
Time87 h105 h
Distance2,034 km stored + approx. 260 km estimated1,880 km
Average ride length68 min92 min
Elevation gain1,180 m (routes)10,080 m

The hours are almost the same, but they are not the same hours. The 105 outdoor hours include descents, traffic lights, stops and long trips, like the 144 km ride to St. Anne's Mountain (Góra św. Anny) where I turned around 1.3 km short of the top (I wrote it up in the piece about my first attempt at St. Anne's Mountain). On the trainer every minute is pedalling at the power the plan sets. Why an hour at home tires you differently than an hour on the road is covered in an hour on the trainer vs an hour outside.

Month by month: autumn belongs to the trainer

0 200 400 600 800 Kilometres per month, 2026 trainer estimate outdoors Mar Apr: estimate 125 km (rides with no stored distance) Apr: outdoors 40.7 km 125 41 Apr May: trainer 147.8 km May: estimate 135 km (rides with no stored distance) May: outdoors 458.7 km 283 459 May Jun: trainer 166.7 km Jun: outdoors 311.7 km 167 312 Jun Jul: trainer 21.7 km Jul: outdoors 78.4 km 22 78 Jul Aug: outdoors 686.3 km 686 Aug Sep: trainer 530.8 km Sep: outdoors 239.7 km 531 240 Sep Oct: trainer 829.3 km Oct: outdoors 64.4 km 829 64 Oct Nov*: trainer 337.9 km 338 Nov* * November: 1–10 Nov only
Kilometres in each month of 2026. Blue bars are the trainer; the hatched part is the estimate for April and May rides that have no stored distance. Green is outdoor riding. Data from WattLog.pro.

The chart splits the year into three parts:

The most important thing for me is that the strongest month of the year was October, not August. Autumn, which usually means the end of the season, gave me my best training block of the year.

Week by week: consistency

0 h 4 h 8 h 12 h Hours on the bike per week trainer outdoors week of 23 Mar: outdoors 1.8 h Mar week of 30 Mar: outdoors 0.9 h week of 6 Apr: outdoors 7.1 h Apr week of 13 Apr: outdoors 2.0 h week of 20 Apr: trainer 2.2 h week of 20 Apr: outdoors 3.3 h week of 27 Apr: trainer 4.1 h week of 4 May: trainer 2.5 h week of 4 May: outdoors 3.7 h May week of 11 May: trainer 7.4 h week of 18 May: trainer 1.1 h week of 18 May: outdoors 6.3 h week of 25 May: outdoors 12.3 h week of 1 Jun: outdoors 7.8 h Jun week of 8 Jun: trainer 2.3 h week of 8 Jun: outdoors 4.9 h week of 15 Jun: trainer 2.0 h week of 15 Jun: outdoors 2.3 h week of 22 Jun: trainer 1.4 h week of 29 Jun: trainer 1.0 h week of 29 Jun: outdoors 1.5 h Jul week of 20 Jul: outdoors 0.7 h week of 27 Jul: trainer 0.9 h week of 27 Jul: outdoors 1.5 h week of 3 Aug: outdoors 3.2 h Aug week of 10 Aug: outdoors 8.9 h week of 17 Aug: outdoors 12.8 h week of 24 Aug: outdoors 9.0 h week of 31 Aug: outdoors 7.6 h week of 7 Sep: trainer 4.4 h week of 7 Sep: outdoors 3.7 h Sep week of 14 Sep: trainer 7.5 h week of 21 Sep: trainer 6.3 h week of 21 Sep: outdoors 1.0 h week of 28 Sep: trainer 6.1 h week of 28 Sep: outdoors 3.0 h week of 5 Oct: trainer 6.4 h Oct week of 12 Oct: trainer 7.7 h week of 19 Oct: trainer 5.3 h week of 26 Oct: trainer 8.2 h week of 2 Nov: trainer 8.5 h Nov 9 weeks in a row, 4–7 trainer rides each July: almost nothing August: outdoors only
Riding hours in each week from 23 March to 8 November 2026. Blue is the trainer, green is outdoor riding. I left out the last, incomplete week. Data from WattLog.pro.

Outdoors, my weeks jumped from zero to almost 13 hours, depending on the weather, holidays and how I felt. Since 7 September, on the other hand, I have 9 weeks in a row with 4–7 trainer rides each, which is 4.4–8.5 hours a week. That is not a lot. But it is every week, and that repetition is exactly what builds fitness. A week with 6 hours of riding is worth more than one 12-hour week after a two-week break. How many hours you need to make progress is covered in how many hours a week to train.

Most of my hours fall on Saturday (20 of 87), because that is when I do the longest ride of the week, usually 1.5–2 hours at an easy pace. Intervals are on Tuesdays and Thursdays. The other days are off or easy.

How does a trainer know how far I rode?

A bike on a trainer does not move, so trainer kilometres are always calculated. In WattLog.pro nobody guesses them: the number comes from two things the trainer or power meter really measures, power and time.

20 25 30 35 40 Flat-road speed, km/h (102 kg incl. bike) 60 W 100 W 140 W 180 W 220 W 260 W 114 W ≈ 27.3 km/h my average: 114 W ≈ 27.3 km/h 193 W ≈ 33.6 km/h my FTP: 193 W ≈ 33.6 km/h Crr 0.004, CdA 0.32 m², no wind
Power vs speed on a flat road in the model WattLog.pro uses. Air resistance grows with the square of speed, so every extra km/h costs more watts. Work it out for yourself in the power to speed calculator.

An example from 7 November: a two-hour workout with a normalized power (NP) of 145 W gave 58.5 km. The same distance goes into the FIT file WattLog.pro sends to Strava, and the same number shows in the Volume card. That way the kilometres in the app and on Strava match.

Why does the card show 2,034 km and not 2,294 km? 13 rides from 24 April–12 May have no stored distance. Those were the app's first weeks. Heart rate and average power survived from those rides, but not second-by-second power. Average power and time give about 260 km, but that is an estimate, not a measurement. So the card does not guess for those rides: it counts them, shows how many there are, and leaves them out of the kilometres. In this article I add that estimate separately.

One thing has to be said honestly: a trainer kilometre is not the same as a kilometre on the road. There is no wind, no corners and no braking, and the model assumes flat tarmac. That is why I compare my rides mainly by hours and by work (kJ, TSS), and treat kilometres as a measure that is good for motivation. What load depends on is explained in what TSS is.

What those hours gave me

+30 WFTP: 163 W in June, 193 W in October
96 → 93 kgbody weight since mid-September
1.85 → 2.08W/kg at FTP, September → October
4,574 TSSof load from the trainer alone

September and October gave the most, once I started riding to a 3+1 plan: three weeks of building, one lighter week, then a test. After one such cycle my FTP went up from 178 to 193 W. I wrote up the whole story, with the honest caveat that the tests were measured by different devices, in the 3+1 plan in practice. How to read load and freshness in the app is shown in the piece about the Form tab.

I weigh 93 kg and I am losing weight slowly, so it is not just FTP that matters to me but also watts per kilogram. The trainer helps a lot here: I can ride long in a low zone, without descents where I do no work and without climbs where, at my weight, it is easy to go over threshold. If you also have a few kilos to lose, read about losing weight by cycling.

How to start: a plan for your first month

You do not have to ride two hours straight away. My typical ride lasted 68 minutes. Three one-hour rides a week is about 13 hours a month, which at about 27 km/h is about 350 km. Over a year that adds up to more than my whole indoor season. This is what my first month would look like if I were starting over:

WeekWhat you doHow long
1Ramp Test to find your FTP and zones, plus 2 easy rides in zone 2approx. 2 h
23 rides: Tuesday 45 min with 3 × 5 min at tempo, Thursday 45 min easy, Saturday 60 min easy2.5 h
33 rides: Tuesday 60 min with 3 × 8 min at tempo, Thursday 60 min easy, Saturday 75–90 min easy3–3.5 h
4Lighter: 2–3 short, easy rides. After it you can start your first real block and test every 4 weeks.1.5–2 h

A few things that worked for me:

If you are still putting your setup together, start with how to start training on a trainer and whether a trainer is worth buying. The list of trainers that work with WattLog.pro is on the compatible trainers page.

Frequently asked questions

How many kilometres is an hour on a trainer?

It depends on power and weight. At 102 kg (me plus the bike), 114 W gives about 27 km/h and 193 W about 34 km/h on the flat. On average I got 26.6 km per hour and 32 km per ride.

Are trainer kilometres real?

Power and time are measured, and the distance is calculated from them as if you were riding on a flat road with no wind. It is an honest measure of the work done, but not the same as a kilometre on the road, where there are descents, wind and stops.

Is the trainer alone enough to stay fit over winter?

For me it was enough to build fitness: the best month of the year and the biggest FTP gain came in autumn, when I rode almost only at home. What matters more than where you ride is whether you ride regularly and to a plan.

Do trainer rides go to Strava?

Yes. After a workout WattLog.pro sends Strava a FIT file with power, heart rate, cadence and the calculated distance, so the kilometres on Strava and in the app are the same. You switch on automatic upload in the settings.

This describes my rides and my results, not individual training advice. If you are just starting out or have health problems, talk to a doctor before harder training.

Data and method

Where the numbers come from. All rides are stored in my WattLog.pro account. I counted completed rides from 1 January to 10 November 2026. Trainer means rides recorded in the app (ERG workouts, routes, Ramp Tests, riding at a fixed gradient): the first on 24 April. Outdoors means 46 rides imported from Strava (1,805 km, 88 h, all with GPS) and 23 TCX files from my bike computer from March–May (17 h, only 2 with a stored distance). No Strava ride overlaps a trainer ride. I checked the Strava summary (4,320 km, 137 activities) on 10 November.

How I counted.

Limitations. This is one person's data. Until mid-September power was measured by the trainer, then by Assioma pedals, and their readings can differ by a few percent (more in the piece about power match). Power on outdoor rides before September was estimated by Strava without a power meter, so I do not compare TSS or kJ between the trainer and outdoor riding.

Sources

  1. Martin JC, Milliken DL, Cobb JE, McFadden KL, Coggan AR. Validation of a mathematical model for road cycling power. J Appl Biomech. 1998;14(3):276–291. doi:10.1123/jab.14.3.276
  2. Allen H, Coggan AR, McGregor S. Training and Racing with a Power Meter. 3rd ed. Boulder: VeloPress; 2019.

Train smarter with WattLog.pro

WattLog.pro collects data from your trainer and shows what's really happening with your fitness.

Try WattLog.pro for free →

← All blog posts