Choose a race distance and goal time or target pace. Get the pace you need and a complete mile or kilometer split table instantly.
Start with a goal finish time or a target pace. Results update as you type.
Use M:SS, MM:SS or H:MM:SS.
| Marker | Target pace | Segment | Cumulative |
|---|
Even pacing is the simplest baseline. Negative and positive strategies here are deterministic planning models, not performance predictions. Course profile, heat, wind, aid stations, fatigue and individual fitness can change sensible race-day pacing.
Enter race distance, target finish time, and the split interval. The calculator distributes the goal time at a constant average pace and shows split and cumulative times.
The table does not predict real race performance or account for hills, aid stations, fatigue, negative splits, or positive splits.
Use the tool first, then use these checks to interpret, verify and hand off the result without displacing the primary workflow.
A small distance mismatch changes every split. Verify whether the target is a standard race distance, a track workout, or a measured route, and keep kilometers, miles, meters, and time format explicit. Do not silently substitute a nearby standard distance for the actual workout.
Equal splits assume constant average pace. Hills, wind, heat, aid stations, turns, surface, fatigue, and race strategy can make even pacing unrealistic. Use the table as a reference line, then adapt the plan to the course and your training context rather than treating every intermediate time as a requirement.
Calculate cumulative targets from the full-precision pace rather than repeatedly adding a rounded split. Otherwise small rounding differences compound over many intervals. If you are writing splits on a band or watch, keep the display precision practical but preserve the full calculation underneath.
Pick an intermediate marker and independently multiply average pace by distance. Confirm that it matches the cumulative table. This simple round-trip check catches minute/second parsing errors and incorrect mile/kilometer assumptions before the table is used in practice.
WebToolArc