Marathon Time Calculator
Marathon Time Calculator
The Marathon Time Calculator estimates your finish time for any race distance when you enter a target pace and the distance to cover. It is the inverse of a pace calculator: instead of deriving pace from a known time, it projects the total time you will need at a chosen pace. This is the planning tool every runner reaches for when signing up for a race.
Knowing your projected finish time turns a vague ambition ("I want to do well") into a concrete, paced goal. A runner targeting a sub-4:00 marathon can work backward: 4:00:00 over 42.195 km is a pace of 5:41 min/km. Training then centers on holding that pace repeatedly in workouts. The calculator supports any distance — 5K, 10K, half marathon, marathon, or a custom training run — in kilometers or miles.
This tool is especially useful for negative-split and even-split planning, setting corral expectations, and sharing realistic goal times with friends and pacing groups. Because it reads pace in either min/km or min/mile, it fits both metric and imperial training plans without manual conversion. It also doubles as a "what-if" engine: change one input — a slightly faster pace, a slightly shorter course — and see the finish-time payoff immediately, which keeps training motivation high.
Runners often underestimate how much a few seconds per kilometer compounds over 42 km. Holding 5:30 instead of 5:41 min/km in a marathon saves about 8 minutes; starting 10 seconds per km too fast can cost far more in the final 10 km as fatigue mounts. The calculator makes these trade-offs explicit before you toe the line.
The tool also fits neatly into three common planning contexts. First, corral seeding: big-city marathons assign start waves by projected finish time, so an accurate projection places you with runners of similar pace and avoids the frustration of weaving through slower traffic or being swept up by faster surges. Second, pacing-group selection: races offer bunny groups at round targets (3:30, 4:00, 4:30), and knowing whether your fitness projects to 3:57 or 4:06 tells you which group to join — and whether to sit just behind it for a safety margin. Third, fuelling strategy: your projected finish time determines how many gels, how much fluid, and how many caffeine doses you will need, since fuelling is planned by time-on-feet rather than by distance. A runner who will be out for 4:15 needs meaningfully more on-course nutrition than one finishing in 3:10.
Enter the race distance and its unit, then your goal pace split into minutes and seconds, and choose whether that pace is per kilometer or per mile. The result appears instantly.
Example 1 — sub-4 marathon. Distance 42.195 km, pace 5:41 min/km. The calculator returns a finish time of 3:59:48 (just under four hours) and an average speed of 7.45 km/h. That is the classic "Boston Qualifier" boundary for many age groups. Note that 5:41 min/km leaves only 12 seconds of margin; most coaches recommend pacing the first half a touch slower to bank energy.
Example 2 — a 10K at 6:00 min/km. Distance 10 km, pace 6:00 min/km. Finish time is 1:00:00 exactly, speed 10.00 km/h. A clean benchmark for tempo effort. If you instead ran the same 10K at 5:30 min/km, the projection drops to 55:00 — a five-minute swing that shows how pace discipline scales with distance.
Example 3 — imperial plan. Distance 13.1 miles (half marathon), pace 8:00 min/mile. Finish time is 1:44:48, since 8:00 × 13.1 = 104.8 minutes. Speed is 7.50 mph. Converting that to km pace (8:00 × 1.609344 = 12:52 min/km) lets you compare directly against metric training partners.
Example 4 — ultramarathon planning. Distance 50 km, pace 6:30 min/km. Finish time is 5:25:00. The same logic scales to any custom distance — enter 100 km at 7:00 min/km and the tool projects 11:40:00, useful for cut-off planning in trail races.
Example 5 — comparing two goal paces side by side. Suppose you are deciding between a 3:45 and a 3:40 marathon. Enter 42.195 km at 5:20 min/km and the tool returns 3:45:02; enter it again at 5:12 min/km and it returns 3:39:26. The eight-seconds-per-kilometer difference is worth roughly five and a half minutes over the full distance — a concrete way to judge whether the faster target is realistic given your recent long-run paces.
Edge cases. A pace of 0 or a distance of 0 returns no result — you cannot project a time for a stationary runner. Very fast paces (under 2:30 min/km) are valid mathematically but unrealistic for endurance events; treat them as interval or treadmill speeds, not race projections. Extremely slow paces (over 15:00 min/km) are valid but may fall outside race cut-off windows. Watch the unit toggle carefully: entering a min/mile pace while the calculator is set to min/km inflates your projected time by about 61% (the ratio of a mile to a kilometer), a common mistake that produces an alarmingly slow — but harmless — result. Re-check the unit before trusting any surprising number.
Finish time is pace multiplied by distance. Working in seconds avoids rounding drift:
where pace_seconds is your minutes:seconds pace converted to seconds, and distance is in the same unit as the pace (km if pace is min/km, miles if pace is min/mile). The average speed is then:
Manual check. For a half marathon (21.0975 km) at 5:30 min/km: pace_seconds = 330, total_seconds = 330 × 21.0975 = 6962 s = 1:56:02. The calculator confirms this. Converting 5:30 min/km to min/mile gives 8:51, and 8:51 × 13.1 = 6962 s — identical, as expected.
Second worked example — full marathon. Take a target of 5:00 min/km over 42.195 km. Convert the pace: 5:00 = 300 seconds. Multiply: 300 × 42.195 = 12,658.5 seconds. Divide by 3,600 to convert to hours: 12,658.5 / 3,600 = 3.516 hours, which is 3 hours, 30 minutes, and 58.5 seconds — a 3:30:59 finish. The average speed is distance over time in hours: 42.195 / 3.516 = 12.00 km/h. Notice that a round 5:00/km pace does not produce a perfectly round marathon time, because 42.195 is not a whole number of kilometers; the fractional 0.195 km adds the extra 58 seconds beyond a clean 3:30:00. This is why marathon splits published in pace bands rarely land on the minute.
Finish times for standard races at common paces (min/km shown; min/mile equivalent in parentheses):
| Pace (min/km) | 5 km | 10 km | Half marathon | Marathon |
|---|---|---|---|---|
| 4:30 | 22:30 | 45:00 | 1:34:39 | 3:09:18 |
| 5:00 | 25:00 | 50:00 | 1:45:00 | 3:30:00 |
| 5:30 | 27:30 | 55:00 | 1:56:02 | 3:51:39 |
| 6:00 | 30:00 | 1:00:00 | 2:06:35 | 4:13:10 |
| 6:30 | 32:30 | 1:05:00 | 2:17:08 | 4:34:39 |
A second table in min/mile for U.S. plans:
| Pace (min/mile) | 5K (3.11 mi) | 10K (6.21 mi) | Half (13.1 mi) | Marathon (26.2 mi) |
|---|---|---|---|---|
| 7:00 | 21:47 | 43:27 | 1:31:40 | 3:03:24 |
| 8:00 | 24:53 | 49:41 | 1:44:48 | 3:29:36 |
| 9:00 | 28:00 | 55:54 | 1:58:00 | 3:55:48 |
| 10:00 | 31:06 | 1:02:06 | 2:11:13 | 4:22:00 |
These assume perfectly even pacing. Real races lose a few seconds per km to crowding, hills, and fatigue, so add a small buffer to any goal time. The gaps also widen with distance: a 5K loses almost nothing to drift, but a marathon can shed 1–3% to second-half fatigue even with good pacing.
A third table shows the time cost of starting too fast — the final-10 km penalty if you average 10 seconds/km quicker early:
| Goal pace | Even-split time | +10 s/km first half | Effective penalty |
|---|---|---|---|
| 5:00/km marathon | 3:30:00 | ~3:38:00 | ~8 min |
| 5:41/km marathon | 3:59:48 | ~4:10:00 | ~10 min |
| 6:00/km half | 2:06:35 | ~2:12:00 | ~5 min |
The penalty grows because the early surplus is borrowed against depleted glycogen; the calculator's even-split figure is the optimistic ceiling, not the expected result.
- Plan for even splits. The calculator assumes constant pace; build a 1–2% buffer for race-day friction.
- Use a tune-up race. Run a shorter race 3–4 weeks out, then extrapolate with this tool to set your marathon goal.
- Convert once, write both. If your plan is in miles, compute the km equivalent here and note both on your wristband.
- Pace by feel zones. Tie your goal pace to heart-rate or RPE zones so you are not staring at a watch constantly.
- Respect terrain. Flat-course times are faster; trail and hilly courses need slower target paces.
- Re-test monthly. Fitness changes; re-run the projection after a fitness block to keep goals honest.
- Bank time carefully. Negative splitting (slightly slower first half) is safer than positive splitting; use the calculator to set a conservative first-half pace you can hold.
- Plan cut-off math. For timed races, enter your slowest sustainable pace and the course distance to confirm you finish inside the limit with buffer.
The projection is a pure arithmetic extrapolation of a single pace. It does not model the physiological cost of holding that pace for the full distance, weather, course profile, or fatigue. Most runners slow in the second half, so even-split projections are best-case. For a more realistic estimate, use a recent race result and add 1–3% for the longer distance.
How accurate is a marathon time prediction?
If based on a recent shorter race at similar effort, it is within 1–3% for most runners. Pure pace math without a real fatigue model overestimates for distances beyond 10K.
What pace do I need for a sub-4 marathon?
4:00:00 over 42.195 km equals 5:41 min/km (9:09 min/mile). Hold that and you break four hours.
Can I use this for a triathlon?
Yes for the run leg — enter the run distance and your planned run pace. It does not model swim or bike segments.
Why does my watch show a different time?
GPS drift and auto-pause differences make watch totals noisy. Use a measured course and this calculator for planning; trust the official chip time on race day.
Should I run negative or even splits?
Even splits are most efficient; mild negative splits (slightly faster second half) are common in elite racing. Avoid starting too fast, which ruins the projection.
Does it work for walking distances?
Yes. Enter your walk pace (10:00–15:00 min/km) and distance; the same math applies.
How do I convert my goal to min/mile?
Switch the pace unit to min/mile and re-enter your km pace × 1.609344, or just let the calculator display both automatically.
What if my race is not a standard distance?
Enter any custom distance in km or miles. The tool projects any length, from a 400 m repeat to an ultramarathon.
Is the speed number useful?
Average speed (km/h or mph) helps compare with cycling or walking efforts and is handy for treadmill interval setup.
How much buffer should I add?
For a marathon, add 1–2% to the calculated time as a real-world cushion unless you have paced the distance before.
Can I use a shorter race to predict my marathon?
Yes, and it is more reliable than pure pace guessing. A common approach is Riegel's formula, which scales a known time by the distance ratio raised to the power 1.06. For example, a 45:00 10K predicts a marathon near 3:28, not 3:09 (the naive 4.22× multiple), because the exponent accounts for fatigue over the longer distance. Use this calculator to check the pace that prediction implies, then confirm it in long runs.
Why do downhill courses produce faster times than the calculator shows?
The calculator assumes a flat, even-effort course. Net-downhill routes like some point-to-point marathons can shave several minutes off an equivalent-effort flat time because gravity assists you. Conversely, courses with significant climbing run slower than the projection; adjust your target pace up or down based on the elevation profile.
Does temperature affect my projected time?
The calculator does not model weather, but heat matters a great deal. As a rough guide, performance degrades noticeably above about 15 °C (59 °F), and a hot, humid marathon can add several percent to your finish time. On a warm day, set a more conservative pace in the calculator rather than trusting your cool-weather goal.
How do I set even 5 km split targets from my goal?
Divide your projected finish time by the number of 5 km segments. A 4:00:00 marathon has roughly 8.44 segments of 5 km; each 5 km should take about 28:26. Print these splits on a pace band so you can check yourself at every 5 km marker and correct early if you are drifting fast or slow.
Last updated: July 19, 2026
UnByte — Independent Software Engineering
Every calculator references authoritative sources — Editorial policy