Race Finish Time Predictor

Previous race distance:

Use a recent all-out result: 5 km, 10 km, half marathon, marathon, or another preset.

Previous race time:

Enter h/m/s, e.g. 0 h 25 m 00 s for a 25:00 5K.

h m

Target race distance:

Choose the race you are pacing next; the estimate and splits update together.

Model exponent (p):

Default 1.06; use 0.90-1.20 only when you know your distance profile.

Condition adjustment: {{ adjust_percent }}%

Keep 0% for comparable conditions; try +5% for heat/hills or -3% for a fast course.

Split table unit:

Choose kilometers for 1 km rows or miles for 1 mi rows plus any final partial split.

Metric	Value	Copy
{{ row.label }}	{{ row.value }}

#	Distance	Split	Cumulative	Copy
{{ row.label }}	{{ row.distance }}	{{ row.split }}	{{ row.cumulative }}

Scenario	p	Adj %	Finish	Δ vs input	Copy
{{ row.label }}	{{ row.exponent }}	{{ row.adjust }}	{{ row.finish }} {{ row.pace }}	{{ row.delta }}

Enter a previous effort and a target distance to render a chart.

Enter a previous effort and a target distance to render scenario comparisons.

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Race finish prediction turns one known performance into a planning estimate for another distance. A runner who can race 5 km in a certain time has shown a recent level of speed and endurance, and that result can be scaled toward 10 km, a half marathon, a marathon, or another common race distance. The estimate is most useful when the earlier race was recent, accurately measured, and run close to full effort.

Distance changes are not just pace multiplication. A 25:00 5 km has an average pace of 5:00 per kilometer, but holding that pace for 10 km would require a different endurance demand. Longer races add fatigue, fueling needs, muscle durability, and pacing discipline. Shorter target races can sometimes look conservative because a runner may be able to sustain a faster pace when the event ends sooner.

Most race predictors use a distance-power relationship rather than a flat pace rule. Finish time rises with distance, and the exponent above the distance ratio represents the slowdown that usually appears as effort duration grows. That exponent is not a fitness score. It is a curve shape, and different runners can sit above or below the common default depending on training history, race distance, terrain, and how well the reference result matches the target race.

Race finish prediction factors
Factor	Why it changes a prediction
Distance gap	Projecting from 5 km to 10 km is less uncertain than projecting from 5 km to a marathon.
Race specificity	A recent all-out race at a similar distance usually predicts better than an old result or workout split.
Course and weather	Heat, humidity, hills, trail footing, wind, and crowding can change the finish without changing fitness.
Endurance base	Longer targets depend on long-run preparation, fueling practice, and late-race durability.

Two runners with the same 5 km time can have different half-marathon or marathon outcomes because the shorter race does not prove the same skills. One may have enough aerobic volume, fueling practice, and restraint to carry speed deep into a long event. Another may have the same top-end speed but lose minutes late because the target distance asks for durability rather than another burst of pace.

Course and weather can move the answer as much as the formula. Heat raises the cost of cooling the body, high humidity makes sweat less effective, hills and trail footing add mechanical cost, and crowded or tactical starts can prevent even pacing. A fast downhill or unusually cool day can move the estimate the other way, but those advantages should be treated carefully because they may not repeat on race day.

A finish prediction is a pacing aid, not proof of readiness. It does not know weekly mileage, long-run depth, injury history, fueling practice, altitude, wind exposure, or official qualifying rules. The most useful reading is a range: a neutral finish, a pace that can be tested in training, and slower or faster scenarios that show how sensitive the target is to assumptions.

How to Use This Tool:

Use a real race result first, then adjust assumptions after the neutral estimate appears. The calculation uses only the values you enter and does not look up official results.

Select Previous race distance and enter the matching Previous race time in hours, minutes, and seconds. Use a chip time or verified race clock when possible.
Choose Target race distance. Presets include 400 m, 800 m, 1500 m, 1 mile, 3 km, 5 km, 10 km, 15 km, 10 miles, half marathon, marathon, and 50 km.
Open Advanced only when the default needs refinement. The default Model exponent (p) is 1.06, with a visible input range from 0.90 to 1.20.
Set Condition adjustment to 0% for comparable course and weather. Use a positive value for harder conditions and a negative value only when the target course is clearly faster.
Pick kilometers or miles for Split table unit. This changes the checkpoint rows, not the predicted finish.
Read Prediction Metrics first, then compare Pace Split Table, Condition Scenario Table, Split Pace Timeline, Scenario Finish Chart, and Pacing Adjustment Map.
When saving or sharing the estimate, keep the target distance, exponent, condition adjustment, and split unit with the result so the number can be reproduced.

Interpreting Results:

The predicted finish is the headline, but the pace usually tells you whether the number is usable. A target can look reasonable as a finish time while requiring a pace that recent training cannot support, especially when projecting from a short race to a much longer one.

The scenario outputs show how much the estimate moves when the exponent and race-day adjustment shift. A tight cluster suggests the target is relatively stable under common assumptions. A wide spread means the finish depends strongly on endurance fade, heat, hills, trail surface, or late-race fatigue.

Race finish prediction outputs and cautions
Output	What it shows	How to use it
`Predicted finish`	The converted target time after exponent and condition adjustment.	Compare it with realistic goals, cutoff times, and qualifying targets without treating it as a guarantee.
`Predicted pace`	The average pace needed over the target distance in both kilometer and mile units.	Check it against workouts, long runs, and sustainable effort before setting race pace.
`Pace Split Table`	Even-pace checkpoints in the selected split unit, including a final partial segment when needed.	Use it as a baseline plan, then adjust for course profile, aid stations, or a negative-split strategy.
`Condition Scenario Table`	Alternative finishes for current inputs, cooler conditions, humidity or heat, hills or trail, and late fade.	Turn the range into A, B, and conservative race-day targets.
`Pacing Adjustment Map`	A sensitivity curve across condition adjustments from `-15%` to `+30%`.	Look for whether the current choice sits in the faster, baseline, or slower window.

The splits are even-distance math. They do not model surges, walk breaks, aid-station stops, GPS drift, pack running, a downhill opening mile, or a planned fast finish. If the target race is long, hilly, hot, or unfamiliar, let the slower scenarios influence the plan.

Technical Details:

A Riegel-style distance-power model treats race time as a curved relationship between distance and duration. If time scaled linearly, doubling distance would simply double finish time. Endurance racing rarely behaves that cleanly, so the exponent makes longer-distance estimates slower than a pure pace carryover.

The condition adjustment is a separate multiplier applied after the distance conversion. The exponent describes the relationship between the two race distances, while the adjustment describes race-day difficulty or advantage. Changing both at once can move the result quickly, so compare one assumption at a time when building a pace range.

Formula Core

t_{2} = round (t_{1} \times {(\frac{d_{2}}{d_{1}})}^{p} \times (1 + \frac{a}{100}))

pace = \frac{t_{2}}{target distance}

In the formula, t1 is the previous finish in seconds, d1 is the previous distance in meters, d2 is the target distance in meters, p is the exponent, a is the condition adjustment percentage, and t2 is the rounded predicted finish in seconds. Mile pace uses 1609.344 meters per mile.

With the default setup, a 25:00 5 km has t1 = 1500 and d1 = 5000. For a 10 km target with p = 1.06 and a = 0, the estimate is round(1500 x (10000 / 5000)^1.06), or about 52:07.

Race finish model settings and effects
Setting or rule	Value	Effect
Default exponent	`1.06`	Common distance-power assumption for running race comparisons.
Exponent input range	`0.90` to `1.20`	Lower values preserve speed better over longer distances; higher values add more fade.
Condition adjustment input range	`-15%` to `+30%`	Negative values speed the converted result; positive values slow it.
Scenario presets	Current inputs, cool day, humid or hot, hilly or trail, late-race fade	Shows how nearby exponent and adjustment choices change the finish.
Sensitivity bands	`97%` and `103%` of the zero-adjustment baseline	Classifies the adjustment map into faster, baseline, and slower windows.

Distance presets use meter values, including exact road-race values for the half marathon at 21097.5 meters and the marathon at 42195 meters. The split table divides the target distance into 1 km or 1 mile chunks, then adds a final partial row when the target is not an exact multiple of the selected unit.

Uncertainty grows when the previous and target distances are far apart. A 10 km-to-half-marathon estimate is usually easier to judge than a 400 m-to-marathon estimate because the energy systems, pacing skills, and preparation demands are closer.

Worked Examples:

5 km to 10 km. A 25:00 5 km with the default exponent and no condition adjustment predicts about 52:07 for 10 km. This is a relatively close projection because both events are common road distances and the endurance gap is moderate.

10 km to half marathon on a warm day. A runner can start with the neutral half-marathon estimate, then add a positive condition adjustment for heat or humidity. The finish and pace slow together, and the scenario chart shows whether that adjustment changes the race goal by seconds or by several minutes.

Half marathon to marathon. A strong half marathon can still overstate marathon readiness when long runs, fueling practice, and late-race durability are missing. If the marathon prediction looks faster than training supports, compare the hilly, humid, and late-fade scenarios before choosing a pace band.

Fast course comparison. A small negative adjustment can represent a flatter, cooler, or faster target course. Use it sparingly, because course advantages often disappear when wind, crowding, GPS error, or pacing mistakes enter the race.

FAQ:

Which previous result should I enter?

Use a recent, accurately measured race run near full effort. A certified road race or track result is better than a workout split, a GPS estimate, or a tactical race where the time did not reflect your current fitness.

Why does the default exponent matter?

The exponent controls how much the estimate slows as distance increases. The default 1.06 is a useful first pass, but runners with unusually strong endurance may fit a lower value and runners who fade over longer races may fit a higher one.

Does a positive condition adjustment mean I am less fit?

No. It represents harder race-day circumstances after the baseline distance conversion, such as heat, humidity, hills, trail footing, altitude, crowding, or likely late fatigue.

Why do marathon predictions from short races often look too fast?

Short races prove speed but not marathon durability. The marathon also depends on long-run preparation, carbohydrate intake, hydration, muscle damage, and pacing restraint over several hours.

Does changing kilometers to miles change the finish prediction?

No. The split unit changes only the checkpoint rows and chart distance labels. The finish estimate still uses the selected target distance in meters.

Why is no prediction showing?

Check that the previous race time is greater than zero and that both race distances are selected. Then reset the exponent to 1.06 and the condition adjustment to 0% before testing other inputs.

Can I use the estimate for qualification planning?

Use it as a planning guide only. Official qualifying standards, timing systems, age-group rules, course certification, and organizer policies decide actual eligibility.

Glossary:

Condition adjustment: A percentage applied after the distance conversion to represent race-day difficulty or advantage.
Distance-power model: A formula where finish time changes by a distance ratio raised to an exponent.
Exponent: The value that controls how much the prediction slows as target distance grows.
Half marathon: A road running distance of 21.0975 km, exactly half the marathon distance.
Predicted pace: The average pace required to cover the target distance in the predicted finish time.
Riegel model: A widely used race-time prediction approach based on a power relationship between distance and time.

References:

Athletic records and human endurance, Peter S. Riegel, American Scientist.
Half Marathon, World Athletics.
Marathon, World Athletics.
Impact of Environmental Parameters on Marathon Running Performance, PLOS ONE.

Race Finish Time Predictor

Predicted Finish Time

Current status

How to Use This Tool:

Interpreting Results:

Technical Details:

Formula Core

Worked Examples:

FAQ:

Glossary:

References:

Race Finish Time Predictor

Predicted Finish Time

Current status

Introduction

How to Use This Tool:

Interpreting Results:

Technical Details:

Formula Core

Worked Examples:

FAQ:

Glossary:

References: