Running Split Calculator
Turn a target distance and pace into consistent split checkpoints, a precise finish time, and an exportable pacing schedule.
Run setup
Use a positive dot-decimal number, such as 5 or 21.0975.
Common checkpoints are 1 km, 1 mile, 400 m, or 5 km.
Live results
Estimated total run time
1:47:03.60
At 8:10 per mile, a 21.0975 km run takes about 1 hour 47 minutes 4 seconds.
Number of full splits
21
Time per full split
5:04.47
Remaining distance
97.50 m
Time for remainder
0:29.69
Average speed
11.82 km/h
Total segments
22
Split schedule
| Segment | Segment distance | Segment time | Cumulative distance | Cumulative time | Time remaining |
|---|
The final row is a partial segment because the half-marathon distance is not an exact multiple of 1 km. All rows assume even pacing.
How to use this running split calculator
What this calculator does. It converts a route length and an even pace – or a route length and target finish time – into a checkpoint-by-checkpoint pacing schedule. Use it to plan kilometer or mile markers for a road race, 400-meter laps for a track session, aid-station timing during a long run, or repeat distances during a controlled workout. It estimates mathematical split timing under a constant-pace assumption. It does not predict fatigue, hills, wind, surface conditions, GPS error, congestion, or an individualized safe training intensity.
When to use it. The schedule is useful before a race when you want a wristband-style list of cumulative times; during training when a coach specifies repeat distances; when converting a familiar pace per mile into kilometer checkpoints; and when checking whether a target finish time implies a realistic pace. Official events may use standardized measured distances and rules, so consult the current World Athletics technical information when exact competition requirements matter.
How to calculate. The calculator opens with a complete half-marathon demonstration: 21.0975 km at 8 minutes 10 seconds per mile, split every 1 km. Its results and validated Excel workbook are available immediately.
- Choose Enter pace when you know your minutes and seconds per kilometer or mile. Choose Enter total time when you know the desired finish time. Switching methods carries the current calculation across so the schedule does not unexpectedly change.
- Replace Running distance and select its unit. Enter the checkpoint length under Split distance and select that unit independently.
- Enter either Pace Minutes, Pace Seconds, and Per distance, or enter Total Hours, Total Minutes, and Total Seconds. Results update live.
- Read the finish estimate, full-split count, per-split time, partial remainder, average speed, and the full schedule. Select Download Excel to export the current typed values and every schedule row.
- Select Reset to clear the demonstration and all calculated content. Excel export is disabled until a new complete valid state is entered.
Input guide. Time input method is required and selects which time fields drive the model. Running distance is a required positive dot-decimal number, for example 21.0975; commas may be used only as thousands separators, not decimal commas. Its unit can be kilometers, miles, meters, or yards. A larger distance increases total time at a fixed pace. Split distance is also required and positive, for example 1 kilometer or 400 meters. Smaller splits create more schedule rows; the calculator limits a schedule to 2,000 segments to keep the page and workbook responsive. Pace Minutes is a required whole number from 0 to 999 in pace mode; Pace Seconds is required from 0 up to but not including 60 and may contain decimals. Per distance selects per mile or per kilometer. Do not type “8:10” into one field – use 8 minutes and 10 seconds separately. In total-time mode, Total Hours is a whole number from 0 to 999, Total Minutes is 0 – 59, and Total Seconds is 0 – 59.999. The combined time must be greater than zero.
Output guide. Estimated total run time is the even-pace finish time. Number of full splits counts complete checkpoint lengths before the finish. Time per full split is the constant time assigned to each complete split. Remaining distance and Time for remainder describe the final partial segment; both are zero when the route divides exactly. Average speed is distance divided by time, displayed in km/h. Total segments includes the remainder row only when a positive remainder exists. In the table, Segment distance and Segment time describe each row; Cumulative distance and Cumulative time show where you should be at that checkpoint; Time remaining counts down to the finish. These are exact identities for the entered constant pace, but real-world performance is an estimate.
Worked example. The first-open example uses 8:10 per mile, which is 490 seconds per 1,609.344 meters. That equals about 0.30447 seconds per meter. Multiplying by a 1,000-meter split gives 304.47 seconds, or 5:04.47 per kilometer. Dividing 21,097.5 meters by 1,000 gives 21 full splits and a 97.5-meter remainder. The remainder takes about 29.69 seconds, and the complete half marathon takes approximately 1:47:03.60. The displayed table and Excel file use the same unrounded model values. NIST documents the relationship between the meter and common length units in its SI units guidance for length.
How the split formulas work
The calculator converts every distance to meters and every time to seconds. Pace becomes seconds per meter. From there, the central relationships are direct:
full splits = floor(running distance ÷ split distance)
remainder = running distance – full splits × split distance
Each cumulative checkpoint is the sum of all preceding segments. This avoids repeatedly rounding displayed times, which can otherwise create drift by the final row. The workbook stores typed numeric seconds and meters and applies spreadsheet number formats for readability.
Metric and U.S. customary choices are converted with fixed factors. For context, NIST provides an official U.S.-to-metric conversion reference. The calculator uses the exact international mile of 1,609.344 meters rather than the rounded 1.61 km approximation used for mental arithmetic.
Interpreting an even-pacing plan
A perfectly even schedule is a baseline, not a command to ignore conditions. A hilly route can produce slower uphill segments and faster downhill segments while preserving the same overall target. Crowded starts, turns, aid stations, heat, and wind also create local deviations. Use cumulative checkpoints to identify the trend rather than reacting aggressively to a few seconds at one marker.
Negative splitting means covering the latter portion faster than the earlier portion. This calculator intentionally does not invent a progressive pace pattern because the correct progression depends on the workout or race strategy. You can still use the even schedule as the central target, then create a conservative early margin and a faster late margin with a coach. Running is vigorous physical activity for many adults; the CDC explains how intensity relates to breathing and heart rate in its physical activity intensity guidance.
Common mistakes include mixing a pace per mile with a split length in kilometers without selecting the correct units, entering decimal minutes instead of minutes and seconds, and assuming GPS distance is identical to a certified course. Keep the same unit semantics throughout your plan and compare cumulative elapsed time at clearly identified markers.