How Milemarq solves pace, splits, and the race math behind them

Pace is time divided by distance, and that one line covers everything else on this page. Milemarq converts whatever you type into metres and seconds first, divides, then shows the answer in the units you asked for. A 3:30:00 marathon is 12,600 seconds over 42,195 metres, which comes out at 8:00 per mile and 4:58 per kilometre. You get both at once, plus the mph and kph equivalent, because the pace you talk about with training partners and the number on a treadmill console are rarely the same unit.

21,097.5 metres, or 13.10938 miles. Calling it 21 km quietly drops 97.5 metres, and at a two hour half that gap is worth about 33 seconds. The marathon has the same problem in a bigger form: 42,195 metres, not 42 km. Milemarq holds the certified values and builds every split row from them.

8:00 per mile, or 4:58 per kilometre, or 12.1 kph if the console speaks metric. The arithmetic is 60 divided by the belt speed in mph, which gives you decimal minutes, then multiply whatever sits after the decimal point by 60 for the seconds. Belt speeds usually step in increments of 0.1 mph, and one step is worth several seconds per mile at the fast end of the dial and a lot more at walking speed. The table above covers the settings most consoles offer, and the calculator handles everything in between.

Because races don't end on a round mile. A marathon is 26.22 miles, so an imperial split sheet gets 26 full rows and then a trailing partial covering the last 0.22, labelled as partial rather than folded quietly into mile 26. That fragment is where a goal time is usually won or lost, and dropping it would make the sheet look tidier than the race actually is. The partial row carries the exact solved finish time, so the bottom of the elapsed column and your target always agree.

They round in opposite directions, deliberately. A split is a pace, a floor you have to hold, so it truncates to the whole second: 8:00 means eight minutes flat or quicker. An elapsed time is a clock reading, so it rounds to the nearest second the way a watch does. Mile 1 of a 3:30:00 marathon takes 480.62 seconds, which prints as an 8:00 split next to an 8:01 elapsed. Both are correct. Milemarq accumulates elapsed time from unrounded values and pins the final row to the solved duration, so the foot of the column reconciles to your finish time with no drift, however long the run is.

No. Every calculation runs in your browser, and nothing goes out over the network to do the maths. No account, no upload, no server that ever sees a pace. The one thing kept between visits is which unit system you used last, stored locally so imperial or metric leads when you come back. Times, distances and split tables aren't saved anywhere.

Yes. Type any distance up to 100 miles, or 160.9 km, in either unit, and the splits table follows it. Presets for the 5K, 10K, half and marathon are there to save you the typing, but the solver treats a preset and a typed distance identically, so nothing about the maths changes when you use one. Long distances get a single adjustment: past 110 rows the interval steps out to every five miles or kilometres instead of every one, with the trailing partial still shown, so a 100 mile plan stays readable instead of becoming a wall of rows.