How are pace and speed calculated?
Pace is elapsed time divided by distance. Speed is distance divided by elapsed time. The system converts between kilometres and miles automatically.
Convert pace, speed, distance, and finish time, then build race projections and cumulative splits.
Workspace
Walk or run details
Switching modes or units carries the current calculated activity across, so the physical distance, pace, and finish time stay aligned.
Constant-pace estimates
| Distance | Predicted time |
|---|---|
| 1 mile | 9:39 |
| 5K | 30:00 |
| 10K | 1:00:00 |
| Half marathon | 2:06:35 |
| Marathon | 4:13:10 |
These are direct constant-pace projections, not performance forecasts. Longer events normally involve different pacing, fatigue, terrain, weather, and stops.
Pacing plan
| Split | Segment | Cumulative distance | Segment time | Cumulative time |
|---|---|---|---|---|
| 1 | 1 km | 1 km | 6:00 | 6:00 |
| 2 | 1 km | 2 km | 6:00 | 12:00 |
| 3 | 1 km | 3 km | 6:00 | 18:00 |
| 4 | 1 km | 4 km | 6:00 | 24:00 |
| 5 | 1 km | 5 km | 6:00 | 30:00 |
Pace is elapsed time divided by distance. Speed is distance divided by elapsed time. The system converts between kilometres and miles automatically.
Yes. The same distance, pace, speed, and time relationships apply to walking, jogging, and running.
They are simple constant-pace estimates. They do not account for fatigue, terrain, weather, stops, or differences between training and race conditions.
The current physical distance and calculated performance are converted into the new unit or input mode. For example, switching 5 kilometres to miles shows about 3.107 miles rather than changing the activity to 5 miles.
A split shows the time for one segment and the total elapsed time at the end of that segment. The final row can be shorter when the activity distance is not an exact multiple of the selected interval.