What your Strava Fitness number actually means (and whether yours is good)

What the Fitness number represents: CTL, a rolling weighted load

Strava Fitness is CTL — a 42-day exponentially-weighted average of daily training load, the same metric TrainingPeaks calls CTL and Intervals.icu calls Fitness [Allen et al. 2019]. It is an accumulated-load index, not a measured fitness value. A 60 means your last six weeks averaged 60 load units a day, nothing more.

The definition is specific. Each day Strava takes that day's training load, blends in a sliver of it, and lets the prior value decay slightly — a 42-day exponentially-weighted moving average that Coggan and Allen named Chronic Training Load [Allen et al. 2019]. The 42-day window descends from Eric Banister's 1970s fitness-fatigue model, whose decay constants were curve-fit against athlete performance data and have survived four decades of validation [Hellard et al. 2007]. Strava, TrainingPeaks, and Intervals.icu all compute the same underlying number; only the label on screen differs.

What feeds the average is daily training load — roughly intensity multiplied by duration. Strava uses TSS-equivalent values when you ride with power and Relative Effort when you don't [Allen et al. 2019]. That input choice changes the number, which is its own topic; our companion piece on whether to trust Relative Effort or TSS for each workout type covers it. For understanding what the integer means, the point is narrower: Fitness is the running average of whatever load Strava scored, not a direct readout of your engine. It rises slowly, because you can only add a little load per day against a six-week average, and it falls faster than it climbed once recent load drops below that baseline — which is why a falling Fitness line can coexist with hard training.

Why it is a personal trend, not a number to compare

Fitness has no universal good value because the same training produces meaningfully different physiological responses across riders [Mann et al. 2014]. The number is scaled to your own load inputs and your own history, so comparing your CTL to another rider's — or to a feed full of them — is comparing two rulers with different units.

Two riders can run the identical eight-week block and arrive at different fitness gains. Mann and colleagues reviewed the literature on high and low responders and found wide inter-individual variation in adaptation to standardized endurance training, driven by genetics, training history, recovery, and measurement factors [Mann et al. 2014]. A CTL of 70 that represents peak form for one rider can be an easy maintenance week for another. The integer carries no information about where it sits on anyone else's scale.

The number is also only as comparable as its inputs. A rider on power and a rider on heart rate are feeding the average different load metrics, so their CTLs are not on the same axis even before physiology enters. Strava's own data shows the platform is fundamentally social — over 135 million athletes, a feed built on kudos and segments [Strava 2024]. That design quietly invites the wrong comparison: reading your Fitness integer against the riders you follow, when the number was never a cross-rider statistic.

This sits inside the broader discipline of using Strava as a training tool rather than a journal. The data layer every cyclist already has only helps if you read your own trend in its own context. Strava syncs and displays the integer; it does not tell you that a 55 is good for your event or a 90 is more than your life can sustain. We built AdaptCycling to read the full history behind the number — your power curve, your consistency, your gaps — and turn it into a plan, rather than leaving you to guess what the integer is worth.

Is my Fitness number good? The honest answer is event-relative

A good Fitness number is the CTL that matches the demands of your goal event, built sustainably and held without breaking you [Friel 2018]. There is no single target. A 50 can be ample for a local crit and thin for a multi-day gravel race, so the useful question is always good for what, not good in the abstract.

Friel's periodization framework anchors the right way to read the number: you reverse-engineer the load your goal event demands and build toward it across a season [Friel 2018]. A flat 90-minute crit asks less accumulated load than a 200-kilometer gravel event with 3,000 meters of climbing. The CTL that leaves you race-ready for one is under-built or over-built for the other. The number is good when it lines up with what you are training for — not when it clears some round threshold you saw in a forum.

Coaching convention offers loose ballparks, and they are worth stating with the caveat that they are coaching-grade reference points, not validated cutoffs. Many time-crunched amateurs sustain a CTL in the 40 to 60 range; serious enthusiasts training 8 to 12 hours a week often live in the 70 to 90 range; and figures above 100 generally belong to riders with the time and recovery capacity of near-professionals. These are rough orientation only — your sustainable number depends on your inputs, your hours, and how you personally respond [Mann et al. 2014].

The more useful frame than any single target is a readiness band: roughly where your Fitness should sit in the final weeks before your event, given how it has trended. A number climbing steadily toward an event-appropriate level weeks out is good. The same number reached by a panicked late spike, or drifting well below where your event demands, is not — regardless of the digits. Good is a trajectory relative to a goal, which is exactly the judgment the chart cannot make for you.

The decisions actually worth making from it

The Fitness number earns its place by informing four decisions: whether your load is trending toward your event, whether you are building at a sustainable rate, when to back off, and when you are ready to peak [Friel 2018]. Read it as a multi-week slope, never as a daily verdict.

First, direction relative to the goal. In base and build phases you want the line climbing, because a rising CTL means you are accumulating load faster than you are shedding it [Allen et al. 2019]. If your event is twelve weeks out and the number is flat, the plan is not progressing. That is a real signal worth acting on — distinct from a single low ride, which moves the 42-day average by only one to three points and is noise.

Second, rate. The number going up is good only if it is going up sustainably; a CTL that spikes too fast is a load you have not earned the recovery for, and that is where injury and illness risk climb [Foster 1998]. Chase the integer upward too aggressively and you buy a number you cannot hold. How fast is too fast is its own question, owned by the broader self-coached training literature rather than the Strava data layer.

Third and fourth, backing off and peaking. When Fitness has climbed for several weeks, the number itself is your cue that adaptation is banked and a lighter week is due — and when you taper, the integer is supposed to fall while you arrive fresh, which is the plan working, not failing. Both of those readings depend on pairing Fitness with Form, the freshness side of the same chart, which the parent pillar on training with Strava lays out. The single rule that survives all four decisions: the number is a slope you read over weeks, and reading it daily is how riders talk themselves into bad training.

Quick answers

Sources cited in this guide

1. 01
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
2. 02
   Hellard et al. 2007. Assessing the limitations of the Banister model in monitoring training. Journal of Sports Sciences.
3. 03
   Friel 2018. The Cyclist's Training Bible (5th ed.). VeloPress.
4. 04
   Mann et al. 2014. High responders and low responders: factors associated with individual variation in response to standardized training. Sports Medicine.
5. 05
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
6. 06
   Strava 2024. Strava Year in Sport Trend Report 2024. Strava.

More inside Training with Strava

Other articles in this series

1. 01

   Apps that connect to Strava: read vs display

   How to tell which training apps actually read your Strava data and adapt versus the ones that only display your rides.

   →
2. 02

   Is Strava Premium worth it for a self-coached cyclist?

   What Strava Premium gives a training-focused rider, what it doesn't (no coaching), and when the free Intervals.icu chart beats paying.

   →
3. 03

   Relative Effort vs TSS: which to trust by workout

   A per-workout-type rule for when to trust Strava Relative Effort vs power-based TSS, and why they are not the same units.

   →
4. 04

   How to set up Strava for training: one-time configuration

   Configure Strava once for training: real FTP and max HR, honest zones, one sensor stack, and feed privacy that protects your plan.

   →
5. 05

   Strava segments as fitness tests: map efforts to tests

   Use Strava segments as scheduled benchmark tests: which profiles map to which test, how to schedule every 4-6 weeks, and controlling variables.

   →
6. 06

   What to look at on Strava after a ride: 4 metrics

   A 30-second post-ride routine: the four Strava metrics that matter after every ride, the ones to ignore, and why.

   →
7. 07

   Strava Fitness going down while training hard: the decay math

   Why your Strava Fitness (CTL) drops even when you train hard: the 42-day EWMA decay math, the real causes, and when a falling line is correct.

   →
8. 08

   Strava indoor power vs outdoor HR: Fitness chart jumps

   Mixing power-based TSS and HR-based Relative Effort splices incompatible units into your Strava Fitness chart. Why it jumps and how to fix it.

   →
9. 09

   Heart rate drift on long rides at same power: what it means

   Why heart rate climbs at flat power on long rides — cardiovascular drift, aerobic decoupling (Pw:HR) as a durability signal, and what to do.

   →
10. 10

    Strava heart rate zones wrong: the whole-dashboard cascade

    How a wrong max HR in Strava cascades into bad zones, Relative Effort, and Fitness — and how to set zones from real data.

    →
11. 11

    Why your Strava Relative Effort is high on easy rides

    Relative Effort can spike on a genuinely easy ride — usually a mis-set max HR, not lost fitness. What inflates it on Strava and what to do.

    →