Training Stress Score (TSS) Calculator

Calculate your workout's training load based on duration, intensity, and your Functional Threshold Power (FTP).

min
W
W

Quick Facts

TSS of 100
1 hour at FTP
Baseline reference
Recovery Ride
TSS < 150
Low training load
Moderate Workout
TSS 150-300
Some fatigue next day
Hard Workout
TSS > 300
2+ days recovery needed

Your Results

Calculated
Training Stress Score
0
TSS points
Intensity Factor
0.00
NP / FTP ratio
Work Done
0
kilojoules (kJ)

Training Zone

Calculate your TSS to see your training zone.

Frequently Asked Questions

How do I find my FTP?

The most common method is the 20-minute FTP test: warm up, then ride as hard as you can sustain for 20 minutes. Your FTP is approximately 95% of your 20-minute average power. Many apps like Zwift and TrainingPeaks can estimate FTP from your ride data.

Can I use TSS without a power meter?

Yes, alternatives exist. hrTSS uses heart rate data, rTSS (running TSS) uses pace and heart rate, and sRPE (session RPE) multiplies perceived exertion by duration. However, power-based TSS is the most accurate.

What's a good weekly TSS for beginners?

Beginners should start with 200-300 weekly TSS and increase by no more than 10% per week. Listen to your body and prioritize consistency over high volume. After 6-12 months, you can gradually increase to 400-500 TSS/week.

Why is my TSS different from what my bike computer shows?

Differences usually come from varying FTP values. Ensure your FTP is up-to-date in all devices. Also, some platforms use slightly different NP algorithms. For consistency, stick to one platform for TSS tracking.

How does altitude affect TSS?

Power-based TSS doesn't directly account for altitude. However, riding at altitude is harder (lower power output for the same perceived effort), which naturally results in lower TSS. Some coaches apply an altitude correction factor of 2-5% per 1000m elevation.

Should I track TSS for every workout?

For serious training, yes. Tracking TSS for all cycling workouts helps you understand your training load over time. For casual riders, tracking weekly totals is sufficient to avoid overtraining.

What is Training Stress Score (TSS) and how is it calculated?
Training Stress Score (TSS) is a metric that quantifies the overall training load of a workout by combining both duration and intensity. It was originally developed by Dr. Andrew Coggan and Hunter Allen for cycling power-based training, but the concept has been extended to running, swimming, and other sports. Core formula: TSS = (Duration in seconds × NP × IF) / (FTP × 3600) × 100. Where: Duration = workout length in seconds. NP = Normalized Power (a measure of the metabolically equivalent average power, accounting for power variability). IF = Intensity Factor = NP ÷ FTP. FTP = Functional Threshold Power (the maximum power sustainable for ~60 minutes). 3600 = seconds in an hour. Key insight: a workout at exactly threshold (IF = 1.0) for exactly 1 hour produces exactly 100 TSS. This makes TSS intuitive: 50 TSS = a moderately easy session. 100 TSS = a hard 1-hour threshold session. 150 TSS = a very hard session (e.g., hard 90-minute ride at high IF). 300+ TSS = epic (e.g., a 5-hour race or event). Running equivalents: for running without power meters, TSS can be estimated using: running TSS (rTSS) based on pace vs. threshold pace and heart rate. Normalized Graded Pace (NGP) accounts for hills, similar to how NP accounts for power variability. Simplified versions: many tools (Garmin, TrainingPeaks, Strava, Wahoo) calculate TSS automatically from HR or power. The "effort score" / "training load" shown in consumer platforms is often a simplified TSS variant. Why TSS matters: it enables quantitative training load management — you can track week-by-week TSS totals, avoid overtraining, and time peaks for races using the CTL/ATL/TSB model (fitness/fatigue/form).
What is the difference between CTL, ATL, and TSB?
CTL, ATL, and TSB form the Performance Management Chart (PMC) model, originally developed by Eric Banister and later adapted for cycling by Coggan. These three metrics together allow athletes and coaches to quantitatively manage fitness, fatigue, and race readiness. CTL (Chronic Training Load) = "Fitness": CTL is a rolling weighted average of your TSS over the past ~42 days (6 weeks). It represents your fitness base — how much training your body is adapted to sustaining. Calculation: exponential weighted moving average with 42-day time constant: CTL today = CTL yesterday + (TSS_today − CTL_yesterday) × (1 − e^(−1/42)). Interpretation: CTL 40–60: solid amateur base. CTL 70–90: competitive amateur/triathlete. CTL 100–150+: elite or professional athlete. ATL (Acute Training Load) = "Fatigue": ATL is a rolling weighted average of TSS over the past ~7 days. It represents your current accumulated fatigue. Calculation: same formula with 7-day time constant. ATL rises quickly when you train hard and drops quickly when you rest. TSB (Training Stress Balance) = "Form": TSB = CTL − ATL. TSB interpretation: TSB = 0: trained as much as you're adapted to — neutral. TSB positive (+10 to +25): fresher than your fitness base — optimal for racing. TSB negative (−10 to −30): accumulated fatigue — typical during heavy training blocks. TSB very negative (−40 or below): excessive fatigue — risk of illness, injury, or overtraining. How to use for race preparation: the taper: in the 2–3 weeks before a key race, reduce training volume to allow ATL to drop (reduce fatigue) while CTL stays high (fitness is maintained). Goal: TSB of +10 to +25 on race day. The build: during preparation phases, CTL increases gradually (5–10 points per week maximum). ATL exceeds CTL during hard training blocks → TSB goes negative (normal overreaching). Recovery weeks: planned easy weeks allow ATL to drop toward CTL, TSB recovers.
How do I set my FTP and why does it matter for TSS?
Functional Threshold Power (FTP) is the cornerstone of power-based training and TSS calculation. All TSS values are relative to your FTP — if FTP is wrong, every TSS value is wrong. What FTP is: FTP is the maximum average power (in watts for cycling; equivalent pace for running) you can sustain for approximately 60 minutes at full effort. It represents the transition between aerobic and anaerobic metabolism — working at or above FTP accumulates lactate faster than it can be cleared. Methods to estimate FTP: 1. 60-minute all-out test: ride or run at maximum sustainable effort for 60 minutes. Average power/pace = FTP. Most accurate but very fatiguing. Best done on a track or flat course. 2. 20-minute test (most common): ride 20 minutes all-out. FTP estimate = 95% of 20-minute average power (the 5% discount accounts for going harder in 20 min than sustainable for 60 min). Protocol: 10-min warm-up → 5 min full effort → 5 min recovery → 20 min all-out → cool down. 3. Ramp test: gradually increase power/pace until failure. FTP = 75% of the maximum 1-minute power achieved. Less fatiguing; popular in apps like TrainerRoad. 4. Sub-maximal protocols: some devices (Garmin, Wahoo, Polar) estimate FTP/threshold pace from daily training data. Less accurate but requires no dedicated test. How often to re-test: retest FTP every 6–8 weeks during training blocks, or when you notice workouts feeling consistently easier (fitness has improved) or harder (fatigue/illness). For running: FTP equivalent is threshold pace or lactate threshold pace — the pace you could sustain for ~1 hour at maximum effort. Running TSS (rTSS) is calculated using threshold pace instead of FTP. Common mistake: setting FTP too high (making yourself feel slower/less powerful than you are) or too low (making easy workouts seem harder than they should). Accurate FTP testing and honest effort are the foundation of the entire training load model.
How much TSS should I accumulate per week?
Weekly TSS targets depend on your sport, training phase, fitness level, and schedule. General guidelines for cycling and triathlon: beginning athlete (< 1 year of training): 200–350 TSS/week. Intermediate (1–3 years): 300–600 TSS/week. Advanced amateur / competitive age-grouper: 500–800 TSS/week. Elite amateur: 700–1,000+ TSS/week. Professional: 1,000–1,500+ TSS/week. Weekly TSS by training phase: base/endurance phase: lower intensity, higher volume — target CTL building at 3–5 points/week. Build phase: add intensity — higher ATL, some negative TSB expected. Peak/race prep: reduce volume to allow TSB to rise. Recovery weeks (every 3–4 weeks): 50–60% of normal TSS to allow adaptation. Increasing weekly TSS safely: the "10% rule" for TSS: don't increase weekly TSS by more than 10% per week. For CTL building: increasing CTL by more than 5–7 points/week is generally too aggressive. Rapid CTL increases (> 10 points/week) are associated with higher injury risk. Signs you're accumulating too much TSS: declining HRV (Heart Rate Variability). Worsening heart rate recovery. Persistent fatigue that doesn't resolve with a rest day. Declining performance in workouts. Increased susceptibility to illness. Monitoring strategy: use weekly TSS + CTL/ATL/TSB tracking (TrainingPeaks, Garmin Connect, Intervals.icu — free). A weekly TSS of 0 on rest days is intentional, not a failure. The recovery stimulus is as important as the training stimulus — TSS × 0 days are where the adaptation happens.

Key Takeaways

  • TSS quantifies your workout's training load combining duration and intensity
  • A TSS of 100 equals one hour of riding at your Functional Threshold Power (FTP)
  • Use TSS to balance training stress and recovery for optimal performance
  • Weekly TSS totals help prevent overtraining and guide periodization
  • Intensity Factor (IF) shows how hard you worked relative to your FTP

What Is Training Stress Score (TSS)?

TSS per Session Interpretation Recovery Time
0–50Low — recovery or easy workout< 24 hours
50–100Moderate — productive training24 hours
100–150High — hard training session24–36 hours
150–200Very high — heavy load36–48 hours
> 200Extreme — epic training48–72+ hours
Note: TSS values above 100 for a single session are unusual and should only occur during long race-simulation efforts or long endurance events. Consistently high single-session TSS without adequate recovery leads to overtraining.
Metric Description Calculation Notes
CTL (Fitness)Rolling 42-day average of daily TSSExponential weighted moving average (42-day)Represents your fitness base
ATL (Fatigue)Rolling 7-day average of daily TSSExponential weighted moving average (7-day)Represents accumulated fatigue
TSB (Form)CTL minus ATLTSB = CTL − ATLPositive = fresh; negative = fatigued
Sweet spot training zoneCTL 50–80Sustainable for most amateur athletesBuild here before increasing volume
Elite athlete CTLCTL 100–150+Requires years of base and high training volumeNot achievable without periodization
TSB for race day+10 to +25Target for peak race performanceAchieved by tapering (reducing ATL)
TSB during heavy training−20 to −40Normal overreaching stateNot sustainable long-term
Training Zone Intensity Factor (IF) Typical Effort Example Activity
Zone 1 – Recovery0.00–0.55Very easy / active recoveryEasy spin, walk
Zone 2 – Endurance0.55–0.70Long easy aerobic effortLong slow run, easy ride
Zone 3 – Tempo0.70–0.80Moderate sustained effortTempo run; marathon pace
Zone 4 – Lactate threshold0.80–0.90Hard sustained effortHalf-marathon to 10K pace
Zone 5 – VO2max0.90–1.00Very hard; near maximum5K race pace; VO2max intervals
Zone 6 – Anaerobic> 1.00Maximum effortSprints; short intense intervals
Note: IF = Normalized Power (or pace equivalent) ÷ Functional Threshold Power (or pace). An IF of 1.0 means you trained at exactly threshold. A 60-minute effort at IF 1.0 = 100 TSS.

Training Stress Score (TSS) is a metric developed by Dr. Andrew Coggan and Hunter Allen to quantify the overall training load of a workout. It takes into account both the duration and intensity of your ride, providing a single number that represents how much stress the workout placed on your body.

TSS is essential for cyclists, triathletes, and endurance athletes who use power meters to track their training. By monitoring TSS, you can optimize your training load, prevent overtraining, and plan effective recovery periods.

The TSS Formula Explained

TSS = (Duration x NP x IF) / (FTP x 3600) x 100
Duration = Workout time in seconds
NP = Normalized Power (watts)
IF = Intensity Factor (NP/FTP)
FTP = Functional Threshold Power

The formula can be simplified to: TSS = (Duration in hours) x IF2 x 100. This shows that intensity has a squared effect on TSS, meaning a workout at IF 0.9 produces significantly more stress than one at IF 0.7.

Understanding TSS Zones

TSS Range Training Load Recovery Time Description
< 150 Low Same day Recovery ride, easy endurance
150 - 300 Medium Next day Standard training session
300 - 450 High 2 days Hard workout or long ride
> 450 Very High 2+ days Race or extreme effort

What Is Normalized Power?

Normalized Power (NP) represents the power you could have maintained for the same physiological cost if you had pedaled smoothly at a constant effort. It accounts for the fact that variable power (intervals, hills, surges) is more stressful than steady power.

Most cycling computers and apps like Garmin, Wahoo, and TrainingPeaks automatically calculate NP from your power data.

What Is Intensity Factor?

Intensity Factor (IF) is the ratio of your Normalized Power to your Functional Threshold Power (NP/FTP). It tells you how hard you worked relative to your maximum sustainable effort:

  • IF < 0.75: Recovery or endurance pace
  • IF 0.75 - 0.85: Tempo effort
  • IF 0.85 - 0.95: Threshold work
  • IF 0.95 - 1.05: Anaerobic/VO2max intervals
  • IF > 1.05: Short, maximal efforts

Pro Tip: Weekly TSS Guidelines

Most athletes can handle 400-600 weekly TSS sustainably. Competitive cyclists often accumulate 600-900 TSS/week during build phases. Exceeding your typical weekly TSS by more than 30% increases injury and burnout risk.

How to Use TSS for Training

1. Track Chronic Training Load (CTL)

CTL is your rolling 42-day average TSS, representing your fitness. Gradual increases in CTL indicate improved fitness without overtraining.

2. Monitor Acute Training Load (ATL)

ATL is your rolling 7-day average TSS, representing fatigue. Sharp spikes in ATL suggest you may need extra recovery.

3. Calculate Training Stress Balance (TSB)

TSB = CTL - ATL. A positive TSB means you're fresh (good for racing), while a negative TSB indicates accumulated fatigue (fine during training blocks).

4. Plan Recovery Weeks

Every 3-4 weeks, reduce weekly TSS by 40-50% to allow adaptation and prevent overtraining.

Additional Resources

For more health and fitness calculators, explore our complete collection at Calculator Cloud. We offer calculators for BMI, TDEE, heart rate zones, and many more training metrics to help optimize your performance.

How do I know if my result is in a healthy range?
Reference ranges are provided above or in the calculator's output. These represent population averages — your optimal value may differ based on age, sex, ethnicity, and individual physiology. Use the result as a starting point for a conversation with your healthcare provider.