HealthWavy Smart Health Tools for Everyday Wellness

Calories & Activity · Power-based workload

Cycling Training Stress Calculator

Calculate power-based intensity factor and training stress from duration, normalised power and FTP, with duration and threshold comparisons.

MODEL WORKSPACE

Power-based workload workspace

Power-based model; no recovery score

Example values are shown. Change them to calculate your result.

YOUR RESULT

Your power-based workload

96 power-based stress points

Intensity factor: 0.800

Intensity factor0.8
Duration90 minutes
Normalised power input200 W
FTP input250 W
Full result table
Calculated from the current values, with rounded display.
Duration minIntensity factorStress points
150.816
300.832
600.864
900.896
900.896
1200.8128
1800.8192

Power-based model only; not heart-rate TSS, running stress or an injury-risk score. It depends on valid NP and FTP inputs. These metrics originated with TrainingPeaks; this independent calculator is not affiliated with TrainingPeaks.

HEALTHWAVY AI

Let’s work it out.

Ask about this tool, enter your values, or understand your result.

Ask in your own language.

GET STARTED

How to use Cycling Training Stress Calculator

  1. Use a normalised-power value from suitable ride data.
  2. The same intensity factor produces more total stress as duration increases.
  3. The result summarises a power-based training record.

Worked example

90 minutes at 200 W normalised power with FTP 250 W give IF 0.8 and modelled stress 1.5 × 0.8² × 100 = 96.

Formula, accuracy & limitations

Intensity factor IF = normalised power / FTP. Power-based stress = duration(hours) × IF² × 100. Equivalent expression: seconds × NP × IF / (FTP × 3600) × 100.

Power-based model only; not heart-rate TSS, running stress or an injury-risk score. It depends on valid NP and FTP inputs. These metrics originated with TrainingPeaks; this independent calculator is not affiliated with TrainingPeaks.

These outputs use the stated model and your supplied inputs. A mathematically consistent model can still differ from personal measurements. Scenario curves and formula comparisons are not statistical confidence intervals.

Source and method context ↗

Enter normalised rather than average power

Use a normalised-power value from suitable ride data. Average power and normalised power answer different questions when output varies. Keep watts consistent and enter a current FTP estimate from a compatible test or measurement method.

Read intensity and duration separately

The same intensity factor produces more total stress as duration increases. The duration curve holds intensity fixed, while the FTP sensitivity comparison holds the ride fixed. A lower entered FTP increases the model score even if the physical ride does not change.

Keep the score in its model context

The result summarises a power-based training record. It does not know sleep, illness, heat stress or injury history and cannot certify recovery. Compare repeated rides only when the input methods and threshold assumptions remain reasonably consistent.

Check the threshold sensitivity before comparing rides

A 90-minute ride at normalised power 200 W and FTP 250 W produces intensity factor 0.8 and 96 stress points. Changing only FTP to 225 W raises intensity factor to 0.888889 and the score to about 118.518519. The ride data did not change. This demonstrates why historical comparisons can shift when the chosen threshold changes. Preserve the threshold assumption used for the original record or recalculate consistently before attributing a score difference entirely to a harder ride.

QUICK ANSWERS

Frequently asked questions

Why is one hour at FTP equal to 100?

That follows directly from the model: one hour multiplied by an intensity factor of one squared, then multiplied by 100.

Can I substitute average watts?

That creates a different estimate when power varies. The field specifically asks for normalised power and does not silently treat average power as equivalent.

Can the result exceed 100?

Longer rides or intensity factors above one can produce scores above 100. The calculator does not cap a mathematically valid output.

Does a large score mean an injury is likely?

No injury probability is calculated. This score lacks the personal and clinical information required for that inference.