What Is Training Stress Score (TSS)? A Runner's Complete Guide

What Is Training Stress Score?

Training Stress Score is a single number that answers the question: "How hard was that workout?" It does this by combining two factors that determine how much stress a session places on your body: duration and intensity. A long, easy run and a short, hard interval session might produce similar TSS values, but for entirely different reasons. TSS captures the net physiological cost of each workout in a way that lets you compare sessions side by side.

The concept originated in the cycling world, where Dr. Andrew Coggan developed TSS as part of his power-based training framework. Cyclists had power meters that made precise measurement possible, and TSS gave them a way to quantify training load objectively. Runners have since adapted the concept using pace, heart rate, and perceived exertion as proxies for intensity.

The reference point is simple: a one-hour workout performed entirely at your threshold intensity (roughly your one-hour race pace) equals exactly 100 TSS. Everything else is measured relative to that benchmark. An easy 30-minute recovery jog might produce around 25 TSS. A hard 90-minute tempo run could generate 150 TSS or more. A 20-minute interval session with brutally fast repeats might land at 50 TSS despite being shorter, because the intensity is so high.

This scoring system means you can finally compare apples to oranges. Was yesterday's hill workout harder than Tuesday's tempo run? TSS gives you a concrete answer rather than relying on how you felt, which is influenced by sleep, mood, caffeine, and a dozen other variables.

How TSS Is Calculated for Runners

While the original cycling TSS uses power data, runners have three main approaches to calculating training stress. Each has its strengths, and the best training platforms use multiple methods to cross-validate results.

Pace-Based TSS (rTSS)

Running TSS, or rTSS, uses your threshold pace as the reference intensity. Your threshold pace is roughly the pace you could sustain for a hard one-hour effort. For many recreational runners, this is close to their 10K race pace; for more experienced runners, it might sit between 10K and half-marathon pace.

The calculation hinges on something called the Intensity Factor (IF), which is the ratio of your actual pace to your threshold pace. If you run faster than threshold, your IF is greater than 1.0. If you run slower, it is less than 1.0. The formula works like this: TSS equals the Intensity Factor squared, multiplied by the duration in hours, multiplied by 100.

Here is a concrete example. Say your threshold pace is 5:00 per kilometer, and you go out for a 45-minute run at 5:30 per kilometer. Your Intensity Factor is approximately 0.91 (since 5:00 divided by 5:30 gives you a ratio based on speed, not pace). Squaring that gives you about 0.83. Multiply by 0.75 hours (45 minutes) and then by 100, and you get a TSS of roughly 62. That tells you this was a moderate session, well below the 100-point threshold benchmark.

Now consider a different workout: 60 minutes at your exact threshold pace. IF = 1.0, squared = 1.0, times 1.0 hours, times 100 = exactly 100 TSS. The math checks out with the definition. A 30-minute easy jog at 6:30 per kilometer pace (IF around 0.77) would give you roughly 0.59 times 0.5 times 100, which is about 30 TSS.

Heart Rate-Based TSS (hrTSS)

Heart rate-based TSS uses your lactate threshold heart rate (LTHR) as the reference point instead of pace. The calculation follows a similar structure: your actual heart rate during the run is compared to your LTHR to derive an intensity factor, which is then squared and multiplied by duration.

Heart rate TSS shines in situations where pace is not a reliable indicator of effort. Running uphill at 6:30 per kilometer might demand the same cardiovascular effort as running 5:00 per kilometer on flat ground. On a hot day, your heart rate rises even if your pace stays the same, and hrTSS captures that additional stress. For trail runners, where elevation changes constantly, hrTSS is often the most accurate method available.

The downside is that heart rate responds with a lag. During short, high-intensity intervals, your heart rate may not fully catch up to the actual effort, which can underestimate the stress of very fast repeats. This is why combining both pace and heart rate data gives the most complete picture.

RPE-Based TSS

When you do not have GPS or heart rate data, your own perception of effort is the next best thing. Rate of Perceived Exertion (RPE) on a 1-10 scale, multiplied by the duration of the workout in minutes, gives you a rough training load number. This method is less precise than pace or heart rate, but it is far better than recording nothing at all.

RPE-based TSS is especially useful for treadmill runs where GPS is unavailable, cross-training sessions, or any workout where your watch malfunctions. PeakRunner uses RPE as a fallback method and also as a cross-validation tool. If your pace-based TSS says a workout was easy but your RPE says it was brutal, that discrepancy is worth investigating. It might indicate fatigue, illness, or the beginning of overtraining.

Why TSS Matters for Runners

TSS transforms subjective feelings into objective data. Instead of writing "felt hard" in your training log, you have a number that can be tracked, graphed, and compared over weeks and months. This objectivity is what makes structured training possible.

More importantly, TSS is the building block for the higher-level metrics that truly drive smart training: Chronic Training Load (CTL), which represents your fitness; Acute Training Load (ATL), which represents your recent fatigue; and Training Stress Balance (TSB), which represents your form. These metrics, explained in detail in our CTL, ATL, and TSB guide, are all calculated from your daily TSS values. Without accurate TSS, those downstream metrics are meaningless.

TSS also helps answer the two most common training questions. "Am I doing enough?" If your weekly TSS is consistently low relative to your goals, you probably need to add volume or intensity. "Am I doing too much?" If your weekly TSS has spiked dramatically compared to your recent average, you are at elevated risk of injury or burnout. Monitoring these trends is at the heart of injury prevention in running.

Without TSS, training load management is guesswork. You might feel great one week and terrible the next without understanding why. TSS connects the dots between what you did and how your body responded.

Weekly TSS Guidelines for Runners

While individual variation matters enormously, here are rough weekly TSS ranges based on training volume and experience. Use these as starting points, not hard rules.

These ranges are rough guidelines. A recreational runner training for a marathon will likely push toward the higher end of their range, while a competitive runner in an off-season may drop below 300. Context matters far more than hitting a specific number.

The 10% rule: Do not increase your weekly TSS by more than about 10% from one week to the next. This is a well-established principle in endurance training. If you ran 300 TSS last week, aim for no more than 330 this week. Larger jumps are where injuries tend to happen, because your body needs time to adapt to new levels of stress.

Recovery weeks: Every three to four weeks, plan a recovery week where your total TSS drops to 60-70% of your normal load. If your usual week is 400 TSS, a recovery week would be 240-280 TSS. These reduced-load weeks allow your body to consolidate the fitness gains from the harder weeks. Skipping recovery weeks is one of the most common mistakes that leads to stagnation or injury.

How PeakRunner Calculates TSS Automatically

Calculating TSS by hand is tedious. You would need to export your workout data, determine your threshold pace or heart rate, apply the formula for each run, and update a spreadsheet. Most runners stop doing this after a week or two.

PeakRunner handles this automatically. When you sync your activities from Strava, PeakRunner calculates rTSS from your pace data for every run. When heart rate data is available, it cross-validates with hrTSS to ensure accuracy, especially for hilly or hot-weather runs. For non-GPS workouts like treadmill sessions, you can log your RPE and duration, and PeakRunner estimates your TSS from that.

This daily TSS data then feeds directly into your CTL (fitness), ATL (fatigue), and ACWR (acute-to-chronic workload ratio) calculations. These are the metrics that power your adaptive training plan. When your ACWR climbs too high, PeakRunner automatically adjusts upcoming workouts to keep you in a safe training zone. When your fitness plateaus, it identifies opportunities to safely increase load. No manual spreadsheets, no guesswork.

Common TSS Mistakes Runners Make

Understanding TSS is one thing. Using it well is another. Here are the most common pitfalls:

• Chasing high TSS numbers. It is tempting to treat TSS like a score where higher is always better. But more stress without adequate recovery leads to overreaching and eventually overtraining. The goal is not maximum TSS; it is the right TSS for your current fitness and goals.
• Ignoring the intensity component. A slow three-hour long run might produce 180 TSS. A hard one-hour interval session might also produce 120 TSS. They are different types of stress. The long run builds aerobic endurance; the intervals develop speed and lactate tolerance. TSS tells you the total load, but you still need to ensure the right mix of easy, moderate, and hard efforts across the week.
• Not accounting for non-running stress. TSS only measures the physical stress of your workouts. It does not account for a terrible night of sleep, a stressful day at work, jet lag, or fighting off a cold. Your body does not distinguish between sources of stress. On high-stress days, a workout that would normally feel manageable can push you over the edge. Learning to adjust your training on these days is a skill that separates experienced runners from beginners.
• Comparing your TSS to other runners. A weekly TSS of 400 might represent peak training for one runner and an easy recovery week for another. Threshold paces, training history, age, recovery capacity, and dozens of other factors make direct comparison meaningless. Track your own trends over time instead. Your TSS last month versus this month is infinitely more useful than comparing your numbers to someone else's.