Reading Your Ride Data: A Beginner's Guide

Reading your cycling ride data means turning the numbers from each ride — power, heart rate, cadence, and derived metrics like TSS — into insight about your fitness and the effectiveness of your training. The point is not to collect data for its own sake but to spot trends, confirm that sessions achieved their purpose, and adjust your plan. This guide introduces the key metrics and how to interpret them.

The headline numbers

Every ride file tells a story through a handful of headline metrics. Here is what each means and how to read it.

Metric	What it measures	What to look for
Average power	Simple mean watts	Useful for steady efforts; misleading for variable rides
Normalized Power ($NP$)	Metabolic cost of the ride	Better gauge of effort on group rides and intervals
Average heart rate	Mean cardiovascular response	Compare to power to assess fatigue and drift
Cadence	Pedal revolutions per minute	Consistency and shifts under load
TSS	Training load of the ride	Cumulative fatigue and fitness signal

Average power vs. normalized power

This is the most important distinction for a beginner. Average power is just the arithmetic mean. Normalized Power applies a fourth-power rolling average to capture how variable, surgy efforts feel:

$$NP = \sqrt[4]{\frac{1}{N}\sum \bar{P}_{30}^{\,4}}$$

On a perfectly steady trainer ride, average power and $NP$ are nearly identical. On a group ride with sprints and recoveries, $NP$ sits well above average power — because those surges cost far more fatigue than the average suggests. Always use $NP$ when judging how hard a variable ride was.

Intensity Factor and TSS

Two derived metrics summarize a ride relative to your fitness:

Intensity Factor ($IF$) is the ride's difficulty relative to your threshold:

$$IF = \frac{NP}{FTP}$$

An $IF$ of 1.0 means you rode right at threshold for the duration. A recovery ride is typically below 0.75.

Training Stress Score ($TSS$) combines duration and intensity into a single load number:

$$TSS = \frac{NP \times IF \times 3600}{FTP \times 3600} \times 100$$

Rough TSS benchmarks:

TSS	Ride type
< 50	Easy / recovery
50–100	Typical endurance ride
100–150	Hard interval session
150–200	Long, hard ride or race
> 200	Very demanding; needs recovery

Tracking daily and weekly TSS builds a Performance Management Chart that reveals accumulating fitness and fatigue.

Heart rate: the body's response

Heart rate tells you how your body responded to the work, not the work itself. Useful patterns:

• Cardiac drift. A rising heart rate at constant power over a ride indicates fatigue, heat stress, or dehydration. Mild drift (under ~5%) is normal; large drift signals trouble.
• HR-to-power decoupling. If HR climbs while power holds, you are working harder cardiovascularly for the same output.
• Resting and recovery HR trends. Multi-week trends in resting HR reveal accumulating fatigue or illness.

Cadence

Cadence is less about right or wrong and more about context. Most trained riders self-select 80–100 rpm on flats. Track whether cadence collapses under fatigue — a sign of muscular weakness — and whether you are grinding unnecessarily in heavy gears.

Adding aero and posture data

If you ride with an aero sensor, ride files gain two more dimensions: CdA and posture. The DIDI.BIKE sensor records real-time CdA and posture (via a 100 Hz 6-axis IMU) and syncs to Strava, TrainingPeaks, Garmin, and Wahoo. Reviewing these after a ride tells you not just how hard you worked but how aerodynamically efficient you were, and whether your position held as fatigue set in.

A simple post-ride review routine

1. Check the headline numbers. Did $NP$, $IF$, and TSS match the session's intent?
2. Compare HR to power. Is the relationship consistent, or did HR drift unexpectedly?
3. Look at time-in-zone. Did you spend time where the plan called for it?
4. Review cadence and (if available) posture and CdA. Did form hold under load?
5. Note how you felt. Subjective RPE alongside the data builds calibration over time.

Common mistakes

• Chasing average power. It is easily gamed by coasting and surging. Use $NP$ instead.
• Ignoring context. A high HR on a hot day is not the same signal as on a cool one.
• Over-analyzing single rides. Trends across weeks matter more than any one file.

Putting it together

Reading ride data turns each ride into a data point in a longer arc of training. Pair it with a sound FTP test to keep zones accurate, structured interval design to know what each session should achieve, and the broader Training & Racing data guide for the full framework.

FAQ

What is the difference between average power and normalized power? Average power is the simple mean of all wattage readings. Normalized Power weights surges more heavily via a fourth-power rolling average, giving a better estimate of the metabolic cost of a variable ride.

What is a good TSS for a single ride? A typical endurance ride is around 50 to 100 TSS. Hard interval sessions often reach 100 to 150 TSS. Rides above 200 TSS require significant recovery.

Why is my heart rate lower than expected at a given power? Common causes are fatigue, heat adaptation, dehydration, or simply being well-rested. Tracking cardiac drift over weeks helps distinguish fitness gains from other factors.

Do I need special software to read my ride data? No. Platforms like Strava, TrainingPeaks, Garmin Connect, and Wahoo's app provide power, heart-rate, and TSS analysis. Pairing a sensor like DIDI.BIKE adds CdA and posture data.

References

1. Medicine & Science in Sports & Exercise: Modeling anaerobic work capacity (W') and fatigue dynamics.
2. International Journal of Sports Physiology and Performance: Altitude training block dynamics and VO2max recovery.
3. DIDI.BIKE Technical Reprints: Realtime physiological telemetry and training stress balance tracking.