Set your target pace
Enter the pace that represents the plan for the comparable running work.Enter actual pace
Use the achieved average pace from the same type of work or period.Set weekly distance targets
Enter planned and completed weekly distance in kilometers.Read the two components
The pace component rewards faster-than-target pace; the distance component measures plan completion.Use the composite carefully
The final score is the simple average of the two percentages, so inspect both components before drawing conclusions.
Running Training Load Performance Score Estimator
The Running Training Load Performance Score Estimator creates a simple athlete-specific score from two plan-versus-actual comparisons: running pace and weekly distance completion. It is intended for runners who want one compact indicator showing how current execution compares with their own targets rather than with population norms.
A score near 100 means the entered pace and distance are collectively close to plan. Values above or below 100 indicate over- or under-performance relative to those inputs, but they are not a physiological rating, fitness diagnosis, or standardized coaching metric. Use the component ratios alongside the total score so one strong component does not hide a weak one.
Calculator inputs
min/km
min/km
km
km
Result
—
relative performance score (100 = plan)
Pace component—
Distance component—
Pace difference—
Distance difference—
Pace component = target pace ÷ actual pace × 100Distance component = actual weekly distance ÷ planned weekly distance × 100Performance score = (pace component + distance component) ÷ 2
Where:
- Target pace — planned minutes per kilometer.
- Actual pace — achieved minutes per kilometer; lower is faster.
- Planned distance — weekly distance target in kilometers.
- Actual distance — completed weekly distance in kilometers.
Assumptions: This is a custom, user-relative planning score with equal weighting of pace and distance. It is not a standardized sports-science test, and it does not adjust for terrain, temperature, intensity distribution, fatigue, or race conditions.
What the result means
A value of 100 means the combined pace and distance ratios match the entered plan; the component percentages show where the difference came from.
Do not interpret the score as a medical readiness or injury-risk measure.
Given:
- Target pace: 5.00 min/km
- Actual pace: 5.15 min/km
- Planned distance: 50 km
- Actual distance: 47 km
Calculation:
Pace component = 5.00 ÷ 5.15 × 100 = 97.09%. Distance component = 47 ÷ 50 × 100 = 94.00%. Score = (97.09 + 94.00) ÷ 2 = 95.54.
Result:
95.5 relative performance score.
Interpretation:
The week was about 4.5% below the combined target on this equal-weight model, with both pace and distance slightly under plan.
Is 100 a universal running benchmark?
No. It only means the actual values match the targets you entered. Another runner can receive the same score from very different paces and distances.
Why is target pace divided by actual pace?
Running pace is expressed as time per distance, so a lower actual pace number means faster running. This ratio therefore rises when actual pace is faster than target.
Can the score exceed 100?
Yes. Running faster than target, exceeding planned distance, or both can produce a score above 100.
Should I compare trail and road weeks directly?
Only if the target was set for comparable conditions. Terrain, elevation, surface, and weather can make pace comparisons misleading.
How is this different from training load?
This score compares execution with a personal plan. Training load calculations typically quantify accumulated work or exertion rather than how closely performance matched a target.