Running Volume Progression Calculator

See what weekly growth means for your mileage and each individual run

Find the first week reaching your goal volume

See where a growth rate leads over time

Based on a representative recent week.
Frequency stays the same throughout the projection.
Longest completed run in the past month; at least as long as your starting sessions.
The last step stops at your target.
Your planning assumption, not an injury-prevention rule.
Growth stays at your selected rate, even if the target takes longer.
Edit starting sessions and reference timing

Each run grows in the same proportion. Editing a run updates the weekly total; changing frequency resets the split to equal runs.

Before the first projected week.

Target reached in week 9

Weekly distance20.00to30.00km
Projected weekly volume and session distances at your selected growth rate
WeekWeekly kmRuns (km)ChangeSession review
121.00
6.306.308.40
+5.0%
Compare runs
  • Run 1: -21.3% versus 8.00 km from entered history.
  • Run 2: -21.3% versus 8.00 km from entered history.
  • Run 3: +5.0% versus 8.00 km from entered history.
222.05
6.626.628.82
+5.0%
Compare runs
  • Run 1: -21.3% versus 8.40 km from projected runs.
  • Run 2: -21.3% versus 8.40 km from projected runs.
  • Run 3: +5.0% versus 8.40 km from projected runs.
323.15
6.956.959.26
+5.0%
Compare runs
  • Run 1: -21.2% versus 8.82 km from projected runs.
  • Run 2: -21.2% versus 8.82 km from projected runs.
  • Run 3: +5.0% versus 8.82 km from projected runs.
424.31
7.297.299.72
+5.0%
Compare runs
  • Run 1: -21.2% versus 9.26 km from projected runs.
  • Run 2: -21.2% versus 9.26 km from projected runs.
  • Run 3: +5.0% versus 9.26 km from projected runs.
525.53
7.667.6610.21
+5.0%
Compare runs
  • Run 1: -21.3% versus 9.72 km from projected runs.
  • Run 2: -21.3% versus 9.72 km from projected runs.
  • Run 3: +5.0% versus 9.72 km from projected runs.
626.80
8.048.0410.72
+5.0%
Compare runs
  • Run 1: -21.2% versus 10.21 km from projected runs.
  • Run 2: -21.2% versus 10.21 km from projected runs.
  • Run 3: +5.0% versus 10.21 km from projected runs.
728.14
8.448.4411.26
+5.0%
Compare runs
  • Run 1: -21.3% versus 10.72 km from projected runs.
  • Run 2: -21.3% versus 10.72 km from projected runs.
  • Run 3: +5.0% versus 10.72 km from projected runs.
829.55
8.868.8611.82
+5.0%
Compare runs
  • Run 1: -21.2% versus 11.26 km from projected runs.
  • Run 2: -21.2% versus 11.26 km from projected runs.
  • Run 3: +5.0% versus 11.26 km from projected runs.
930.00
9.009.0012.00
+1.5%
Compare runs
  • Run 1: -23.9% versus 11.82 km from projected runs.
  • Run 2: -23.9% versus 11.82 km from projected runs.
  • Run 3: +1.5% versus 11.82 km from projected runs.

Timing is approximate: starting sessions are placed in the preceding week and all runs are evenly spaced for comparisons. Later references include projected runs, not demonstrated tolerance. Distances are rounded for display.

How it works

Two ways to explore progression

Reach a target finds the first week meeting your goal volume at the growth rate you choose. The final step stops at the target. If it takes longer than the selected horizon, the calculator says so instead of silently increasing the growth rate. Explore progression shows every week within your chosen horizon.

Your weekly total is only part of the picture

The starting sessions grow proportionally, with run frequency held constant. Edit the starting split to compare evenly distributed volume with a week concentrated in one longer run. This is a distance scenario: intensity, terrain, recovery, lighter weeks, and symptoms are not modelled. A chosen weekly growth percentage is a coaching assumption, not a validated injury-prevention rule.

What the session warnings mean

A prospective observational study of 5,205 runners associated individual runs more than 10% longer than the preceding 30-day longest with higher overuse-injury rates. That association is not a personal injury probability. Staying below the reference does not guarantee injury-free progression, and the finding should not automatically be applied to duration or intensity.

Entered history and projected history

Starting sessions are treated as a representative preceding week. The recent longest run is placed one day before the projection by default; change its timing in the expandable inputs if needed. Sessions are evenly spaced for the rolling-window calculation, rather than assigned to calendar dates. Each review identifies whether its longest-run reference comes from entered history or projected sessions. Planned runs do not prove what you can currently tolerate.

All calculations run in your browser without an account. To compare proposed sessions with completed activity history, use Runima's training plan after importing your runs. Its check is stricter: planned sessions never count as history, only completed runs do.

Want these numbers from your own data?

Import your watch data and Runima tracks your fitness, fatigue and race readiness for free.

Create free account