ForHosting KIT · Math

Predict race finish time with Riegel's formula

Predict a finish time for a new race distance from a recent result: a 10 km run in 40 minutes points to a half marathon in 1:28:15, using Riegel's formula with the exponent 1.06. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Known distance
10
Known time seconds
2,400
Target distance
21.0975
You get
Predicted time seconds
5,295.36739456
Predicted time formatted
1:28:15
Distance ratio
2.10975
Exponent
1.06

Turn a trusted race result into a practical prediction for another distance with the classic Riegel exponent formula. Provide the completed race distance, its finish time in seconds, and the target race distance in the same unit. The calculator returns a deterministic predicted duration in seconds and a readable clock format, together with the ratio and exponent used. It is useful for setting an initial goal, comparing race performances, preparing pacing plans, and adding transparent projections to running software. The result is an estimate rather than a promise because training, terrain, weather, fueling, and race execution all affect actual performance.

Enter one reliable race result

Begin with a recent race whose distance and finish time accurately represent your current fitness. For example, forty minutes becomes 2400 seconds, while one hour, thirty minutes becomes 5400 seconds. Both distances must use the same unit: kilometers with kilometers, miles with miles, or meters with meters.

The formula only uses their ratio, so the particular unit does not matter when it is consistent. A ten-kilometer result can therefore predict a half marathon entered as 21.0975, and a 5-mile result can predict a 10-mile race without any conversion. Do not mix ten kilometers with a target written as 13.1 miles, because the numerical ratio would describe the wrong change in distance.

The capability rejects zero and negative distances explicitly, since they cannot describe a race. It also rejects a missing, zero, or negative finish time and any value that is not finite. These checks prevent plausible-looking output from malformed training data.

For the most useful estimate, prefer an all-out result on a measured course over a training run interrupted by stops. A recent event at a broadly similar terrain and elevation profile usually supplies a stronger baseline than an old personal best achieved under very different conditions.

Understand the Riegel calculation

The prediction uses T2 = T1 × (D2 / D1)^1.06. T1 is the known finish time, D1 is the known distance, D2 is the target distance, and T2 is the predicted finish time. If the target is twice as long, the result is slightly more than twice the known time because the exponent 1.06 represents the usual loss of sustainable speed as distance increases.

If the target is shorter, the same relationship works in reverse and predicts a faster average pace. No model is trained on personal records, and there is no random adjustment or hidden athlete profile. Treat the number as a neutral mathematical baseline.

Riegel scaling assumes endurance changes in a regular way, but it cannot know whether an athlete is especially strong at short speed or long aerobic efforts. Larger jumps between known and target distances generally introduce more uncertainty than nearby comparisons, even though the arithmetic itself remains exact.

Use the prediction as a planning range

A race prediction works best as the center of a planning conversation, not as a guaranteed finish. Coaches can start with the calculated time, examine the implied average pace, and then adjust goals for the athlete's training volume, long-run history, recovery, course profile, and expected weather. Runners can compare projections from several recent races to see whether shorter and longer performances tell a consistent story.

If a 5K predicts a much faster marathon than a half-marathon result does, the difference may reveal that endurance preparation matters more than raw speed. Because the calculation is pure and does not contact external services, identical requests remain repeatable and suitable for audited workflows. Validate units before automating batches, and store the original race result beside the prediction so future readers can reconstruct the estimate.

Always communicate the assumptions when sharing a goal with an athlete. Hills, heat, wind, altitude, crowded starts, fueling, injury, fatigue, and changes in fitness can move an actual result substantially. For medical or training-load decisions, use qualified professional guidance rather than relying on this mathematical estimate alone.

Set a target race goal

Convert a recent measured race result into an initial finish-time target for a different distance.

Build pacing software

Generate repeatable finish-time projections for training dashboards, race planners, and coaching tools.

Compare endurance results

Check whether performances at several distances align after applying the same transparent Riegel scaling rule.

What formula does this calculator use?

It uses T2 = T1 × (D2 / D1)^1.06, the classic Riegel race-time prediction formula.

How should I enter the known finish time?

Enter it as total seconds. For example, 45 minutes is 2700 seconds.

Can I mix kilometers and miles in a race time prediction?

No. Both distances must use the same unit, because only their ratio matters. A 10 km result can predict a half marathon entered as 21.0975, but not one written as 13.1 miles.

How accurate is a Riegel race prediction?

It is an estimate, not a promise. Training, terrain, weather, fueling and how the race unfolds all change the real time, so use it as a starting goal and base it on a recent all-out result over a measured course.

Why is the predicted time more than double for a race twice as long?

Because the exponent 1.06 builds in the usual loss of sustainable speed as the distance grows. For a shorter target the same rule works the other way and predicts a faster average pace.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/math/race-finish-time-predict

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/math/race-finish-time-predict \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"known_distance":10,"known_time_seconds":2400,"target_distance":21.0975}'
{
  "known_distance": 10,
  "known_time_seconds": 2400,
  "target_distance": 21.0975
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "math.race_finish_time_predict",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Enter one reliable race result

Supply known_distance as a positive number, then convert the finish time to total seconds for known_time_seconds. Next, enter target_distance as another positive number.

Understand the Riegel calculation

The exponent is fixed so every request is transparent, reproducible, and easy to compare. The response includes predicted_time_seconds, a rounded clock representation, the calculated distance_ratio, the exponent, and the written formula. Floating-point results are cleaned to stable significant precision so the same input produces the same JSON in browser tools, API calls, tests, and spreadsheets. The formatted clock rounds to the nearest whole second for convenient reading, while predicted_time_seconds preserves useful fractional precision.

Use the prediction as a planning range

The API price for a successful item is $0.002; the browser experience may be used for quick interactive checks.

Which distance units can I use?

Any length unit works, provided known_distance and target_distance use the same unit.

What happens if a distance is zero or negative?

The request fails with invalid_input because both known_distance and target_distance must be positive.

How much does an API prediction cost?

Each successful API item costs $0.002.

Read the full KIT documentation →