Race Finish Time Calculator

Current projection

{{ finish_time_local ? `Projected finish clock ${finish_time_local}` : 'Projected finish clock unavailable' }} · Halfway {{ halfwayTimeReadable }}

Avg pace {{ averagePaceDisplay }} · Avg speed {{ averageSpeedDisplay }}

Start Half Finish · {{ routeStageDistanceLabel }}

Preset distance:

Pick a common event, or choose Custom distance after editing the length.

Distance:

Use decimals for certified courses, such as 42.195 km or 26.2 mi.

Input mode:

Choose Pace for pacer bands; choose Speed for treadmill or GPS averages.

Target pace:

Enter minutes and seconds per km or mile, such as 5 min 00 sec per km.

min sec

Target speed:

Enter an average speed with units, such as 12 km/h or 7.5 mph.

Splits by:

Match the course markers or watch alerts: 1 km or 1 mile.

Pacing profile:

Select even, controlled start, negative split, aggressive start, or late fade.

Race start (local):

Leave blank to start from the current local time in your browser.

Chart distance unit:

Choose km or mi for chart exports without changing the race distance calculation.

Effort trend:

Set -15% to 25%; 0% leaves the split ladder neutral.

{{ fatigue_percent }}%

Planned stops:

Use a whole number, such as 3, for pauses included in the race clock.

stops

Stop duration:

Enter seconds per stop, such as 45; set 0 for continuous running.

sec each

Stop spacing:

Choose evenly spaced, front half cluster, or back half cluster.

Cutoff time:

Enter h, m, and s; leave all three at 0 to skip cutoff checks.

h m

Metric	Value	Copy
{{ card.title }}	{{ card.value }} {{ card.note }}
{{ row.label }}	{{ row.value }}
Race note {{ index + 1 }}	{{ item }}

Marker	Distance	Projected clock	Vs base	Note	Copy
{{ row.label }}	{{ row.distance }}	{{ row.clock }}	{{ row.gap }}	{{ row.note }}

Split	Distance	Planned pace	Moving	Stops	Cumulative	Vs base	Copy
{{ row.label }}	{{ row.distance }}	{{ row.pace }}	{{ row.moving }}	{{ row.stops }}	{{ row.cumulative }}	{{ row.gap }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

A useful finish estimate turns a chosen running effort into the clock times a runner, pacer, or crew can act on. Pace says how long one kilometre or one mile should take. Speed says how much distance is covered per hour. Finish time connects those two ideas to the full course distance, then separates the clean moving-time target from the elapsed race clock that keeps running through aid stops, queues, and cutoff checks.

Race distance is the first source of error. A 10 km race, a 10 mile race, a half marathon, and a marathon can look similar in a calendar, but their finish clocks change by large amounts when the unit is wrong. Standard road distances are usually expressed in kilometres, while many watches and training plans use miles. Certified road courses are measured along a defined course line, and a GPS trace often reads longer because runners weave, miss tangents, or record noisy satellite points.

Common race finish time planning terms
Term	Plain meaning	Common mistake
Pace	Minutes and seconds needed to cover one kilometre or one mile.	Reading a per-mile target as per-kilometre, or the reverse.
Moving time	Time spent progressing through the course at the planned effort.	Forgetting that planned pauses still count against elapsed race time.
Gross pace	Average pace across the whole race clock, including stops.	Comparing it directly with a watch pace that excludes stopped time.
Cutoff	The latest elapsed finish time allowed by an event rule.	Checking only average moving pace instead of the full elapsed plan.

Race timeline showing start, halfway, finish, split pace, and race clock checkpoints

Pacing shape matters because the same average effort can be arranged in different ways. Even pacing keeps checkpoints close to the baseline. A restrained start asks for slower early segments and a stronger close. An aggressive start can make early checkpoints look good while leaving a large late slowdown. For longer races, planned stops and course cutoff rules can matter as much as the raw running pace.

A finish estimate is still only a planning model. Heat, wind, hills, crowding, fueling problems, injury risk, and route measurement differences can move the real finish away from a clean split sheet. The most useful plan starts with a simple, correct distance and target effort, then adds stops, pacing shape, and cutoff pressure one assumption at a time.

How to Use This Tool:

Start with the base race clock before adding advanced assumptions. The sliders are useful for scenario testing, while the number fields are better for exact certified distances, watch targets, and race rules.

Choose Preset distance or enter a custom Distance. Check the unit before reading the finish time, especially when switching between kilometres and miles.
Set Input mode to Pace when your target is minutes and seconds per kilometre or mile. Use Speed when your source is a treadmill speed, GPS average, or another distance-per-hour value.
Choose Splits by to match the checkpoints you expect to use. A kilometre ladder is usually better for metric courses, while a mile ladder may match many watch alerts and crew sheets.
Pick a Pacing profile. Use even pace for a neutral first pass, controlled start or negative split for restrained openings, and aggressive start or late fade for stress-testing slower closing segments.
Open Advanced when elapsed race details matter. Set a local start time for projected finish clock, choose the chart distance unit, add effort trend, enter planned stops, choose stop spacing, and add a cutoff time if the event has one.
Read Race Brief first, then inspect Key Markers and Split Plan. Use Pace Shape to see segment pace drift, Race Clock Map to compare projected clock against the base line and cutoff, and JSON when you need a structured copy of the current plan.

Use the copy and download buttons after the plan looks plausible. The brief, marker, and split tables support CSV and DOCX export, while the chart tabs can download chart images or chart CSV data.

Interpreting Results:

Projected finish is the elapsed race duration after the selected pacing shape, effort trend, and planned stops are included. Raw base pace and Raw base speed show the unadjusted target line, so they are the first values to check when the finish looks surprising.

Projected average pace is gross pace. It includes planned stop time, so it can be slower than the moving pace a runner expects to see while running. The Split Plan separates moving time, stop time, cumulative clock, and gap against the base line for each segment.

Race finish result interpretation guide
Output	Read it as	Check before trusting it
`Halfway clock`	Elapsed time at half the selected race distance.	Compare it with the raw base line to see whether the opening half is intentionally slower or faster.
`Opening quarter pace` and `Closing quarter pace`	Average pace across the first and final quarters of the modeled race.	Make sure the gap matches the chosen pacing shape and effort trend.
`Cutoff margin`	Finish cutoff minus projected finish time.	If the margin is small or negative, inspect `Cutoff pace needed` and include planned stops.
`Key Markers`	Quarter, halfway, finish, and common distance checkpoints when they fit inside the course.	Use the notes to spot checkpoints that run ahead of or behind the raw base pace line.
`Race Clock Map`	Projected elapsed time against distance, with the raw base clock as a comparison line.	Watch for late separation from the base line or a cutoff line that sits below the projected finish.

A clean table does not prove the plan is realistic. It proves only that the entered distance, pace or speed, stops, and cutoff values agree mathematically. Use training evidence, course profile, weather, fueling, and event rules to decide whether the target belongs on race day.

Technical Details:

The calculation uses one metric base so that kilometre and mile inputs stay comparable. Distances are converted through metres, pace is normalized to seconds per kilometre, and speed is converted to kilometres per hour before the base finish time is calculated. One mile is treated as 1.609344 kilometres.

The base clock is then adjusted into an elapsed race plan. Effort trend changes the total moving time, split weights redistribute moving time across the course, and planned stops add elapsed seconds where the stop positions fall. Because stop time belongs to the race clock, it slows gross pace even when the moving effort is unchanged.

Formula Core:

The main equations below show the time base, trend adjustment, planned stops, and cutoff comparison. Displayed clocks are rounded to the nearest second.

\begin{matrix} P_{km} & = & \frac{P_{mile}}{1.609344} \\ P_{km} & = & \frac{3600}{V_{kmh}} \\ T_{base} & = & D_{km} \times P_{km} \\ T_{moving} & = & T_{base} \times (1 + \frac{trend}{200}) \\ T_{finish} & = & T_{moving} + (N_{stops} \times S_{stop}) \\ margin & = & T_{cutoff} - T_{finish} \end{matrix}

Race finish formula symbols
Symbol	Meaning	Unit or source
`Dkm`	Race distance after conversion to kilometres.	Preset or custom distance.
`Pkm`	Pace in seconds per kilometre.	Entered directly, converted from per-mile pace, or derived from speed.
`trend`	Effort trend percentage used to lengthen or shorten total moving time.	The visible slider ranges from -15% to 25%.
`Nstops` and `Sstop`	Number of planned stops and seconds per stop.	Advanced stop controls.
`Tcutoff`	Elapsed finish limit used for cutoff comparison.	Hours, minutes, and seconds; zero disables the cutoff check.

Split rows are built from kilometre or mile segments, with the final row shortened when the course distance is not an exact multiple of the chosen split unit. Each segment starts from its raw distance divided by base speed. The pacing profile and effort trend then assign a weight according to where the segment sits in the race. The weighted segment times are scaled back to the adjusted moving total, so the sum of all moving segments still equals the projected moving time.

Race finish pacing profile behavior
Pacing profile	Segment behavior	Planning use
`Even pace`	Keeps segment weights close to the base pace.	Neutral first-pass checkpoint sheet.
`Controlled start`	Adds time to early segments and gives some time back later.	Reducing the risk of an opening surge.
`Negative split`	Makes the early half slower and the closing half faster than the base line.	Planning a second-half build.
`Aggressive start`	Makes earlier segments faster and later segments slower.	Testing how a hard opening affects the finish clock.
`Stable early, late fade`	Keeps early segments near target and adds slowdown mostly after the middle of the race.	Modeling a conservative long-race fade.

Planned stops are placed as evenly spaced positions, a front-half cluster, or a back-half cluster. A stop is charged to the segment where its position falls, which is why one split can show a slower gross pace while the surrounding moving pace remains steady. Key markers include quarter, halfway, three-quarter, common kilometre and mile checkpoints that fit inside the selected distance, and the finish.

The chart distance unit changes only the chart axis labels and exported chart rows. It does not change the race distance, split unit, finish calculation, or cutoff comparison. The cutoff pace needed is a gross elapsed pace across the whole selected distance, so it already includes the race limit rather than only moving time.

Accuracy and Privacy Notes:

Race finish planning depends on assumptions that the calculator cannot verify. It does not inspect course grade, weather, trail surface, congestion, fueling, fitness, injury risk, or official timing rules for a specific event. For record-eligible road races, course measurement and start-to-finish rules can be stricter than ordinary planning needs.

Use certified course distances and official cutoff rules when they are available. Watch distance can be useful after a race, but it is not the same as the measured course line. If a race has intermediate gates as well as a final cutoff, check the event guide because a final finish margin alone may not protect every checkpoint.

The finish, split, marker, cutoff, and chart calculations run in the browser from the values shown on the page. The entered race values are not sent to a dedicated race-prediction service for calculation.

Worked Examples:

A 10 km target pace becomes a finish clock

Choose 10 km (10K), set Input mode to Pace, and enter 5:00 per kilometre. With even pacing, zero trend, and no stops, Projected finish is 50:00, and the halfway clock is about 25:00.

A half marathon target from mile pace

Select the half marathon preset and enter 8:30 per mile. The base finish is about 1:51:26. If Splits by is set to kilometres, each checkpoint still comes from the same 21.0975 km distance, but the split rows display kilometre checkpoints.

Planned stops can decide a cutoff

For a 50 km race, three planned stops of 60 seconds each add three minutes to elapsed finish time. If the Cutoff margin turns negative, Cutoff pace needed shows the gross pace required across the full course, including the stop budget.

FAQ:

Should I enter pace or speed?

Use Pace when your target is a running split such as minutes per kilometre or mile. Use Speed when your source value is in km/h or mph, such as a treadmill setting or GPS average.

Why did my average pace get slower after adding stops?

Projected average pace uses elapsed race time. Planned stops add seconds to the clock, so gross pace slows even when the moving effort stays the same.

Why does the split pace differ from raw base pace?

The split row includes pacing profile, effort trend, and any stop inside that segment. Compare Raw base pace with Opening quarter pace, Closing quarter pace, and the row-level Vs base value.

What should I check when no result appears?

Confirm that distance is positive and that the active pace or speed input is greater than zero. A zero pace, zero speed, missing distance, or wrong unit prevents a valid race clock.

Can this predict my real race result?

It can build a consistent finish-time plan from the values you enter, but it cannot judge fitness, terrain, weather, nutrition, injury risk, or race-day execution. Treat the result as a planning estimate.

Glossary:

Race pace: The time needed to cover one kilometre or one mile at the planned average.
Gross pace: Average pace across elapsed race time, including planned stop time.
Raw base pace: The pace implied by the original pace or speed input before trend, pacing profile, and stop adjustments.
Cutoff margin: The difference between the event cutoff time and projected finish time.
Split plan: The sequence of kilometre or mile checkpoint rows used to map pace through the selected course distance.

References:

Marathon, World Athletics.
Half Marathon, World Athletics.
Technical Rules, World Athletics.
World record criteria for road races, Association of International Marathons and Distance Races.
Pace/Speed, Strava Support.