Sports
Running Split Calculator
Calculate adjusted finish time, average pace, speed, full-split time, checkpoint count, and elevation allowance. The custom track view labels cumulative checkpoint times and preserves a partial final segment instead of rounding the course to whole splits.
Elevation-adjusted planning time (minutes)-
Required average pace (min per km)-
Required average speed (km per h)-
Target time per full split (minutes)-
Number of timing splits-
Modeled elevation allowance (minutes)-
Decision view
Cumulative race checkpoint plan
Cumulative race checkpoint planCourse distance, full splits, a partial finish segment, and cumulative target times share one track.
Exact scenario comparisonTarget finish time (minutes) changes while all other entered assumptions remain constant.
| Target finish time (minutes) | Elevation-adjusted planning time (minutes) | Required average pace (min per km) | Required average speed (km per h) | Target time per full split (minutes) | Number of timing splits | Modeled elevation allowance (minutes) |
|---|
Split-by-split detail
Target pace and checkpoint schedule
How to use Running Split Calculator
- Enter the official course distance and a realistic moving-time target.
- Choose a split length that matches course signage or watch auto-lap behavior.
- Use cumulative checkpoints as pacing references, then adapt for terrain, congestion, weather, fueling, and fatigue.
Calculator guide
Understanding Running Split Calculator
A split plan divides a target distance into repeatable checkpoints. Elevation allowance is added to the entered finish target first, so every cumulative marker and partial final split reconciles to one adjusted race time.
Calculation method
How the calculation works
Convert the target time to an average pace, apply an optional elevation allowance, and build cumulative timing checkpoints at the selected split distance. Add the entered time adjustment per elevation unit, divide adjusted time by course distance for pace, and multiply that pace by each split distance through the finish.
Race execution
Turn checkpoint arithmetic into a usable plan
A good split sheet supports decisions without forcing an unsuitable pace.
Worked situations
Practical examples
- A 10 km target of 50 minutes gives a base pace of 5:00 per km before adjustment.
- At 1 km splits, cumulative targets are 5:00, 10:00, 15:00, and so on.
- If the course ends between full split markers, the final checkpoint is shorter but still lands on the adjusted finish.
Better inputs
Useful tips
- Match distance and split units; convert miles and kilometres before entry.
- Plan effort rather than rigid speed on rolling or technical courses.
- Allow GPS error and course tangent differences when comparing a watch with official markers.
Before relying on the result
Limitations and common mistakes
- The model spreads adjusted time evenly and does not simulate fatigue, wind, heat, aid stops, terrain sequence, or negative splits.
- Elevation adjustment is a user-entered planning factor, not a physiological prediction.
- Race-day performance can differ materially from the schedule.
Reference
Key terms
- Split
- Time for a defined segment of the total distance.
- Cumulative split
- Elapsed target time at a course checkpoint.
- Pace
- Time required per unit distance.
- Elevation allowance
- Entered time added for the course's elevation gain.
Important note
Calculated from the entered performance values using the displayed method. Health, fitness, terrain, weather, equipment, and event conditions can change real-world outcomes.
Frequently asked questions
Are the displayed splits cumulative?
The custom track labels cumulative target time at each checkpoint.
What if the distance is not divisible by the split length?
A shorter final segment is retained and ends at the exact course distance.
Does elevation automatically predict slower pace?
Only through the adjustment factor entered by the user.
Can this make a negative-split plan?
Not directly; use the even schedule as a baseline and redistribute segment times manually.