Race Time Prediction: What Finish Time Is Realistic?

"What time are you running on Sunday?" — few questions get such a vague answer from runners. Overly optimistic goal times end in a collapse over the final kilometres; overly conservative ones leave you with the feeling you gave something away at the finish line. The good news: from a recent personal best, your realistic race time can be calculated with surprising accuracy — if you know the right method and respect its limits.

Why a realistic goal time matters so much

A goal time is not a number for the results list — it is the control variable for the entire race. It determines your starting pace, and the starting pace decides your energy budget: going just ten seconds per kilometre too fast in the first half of a marathon typically costs you double that on the second. An analysis of more than two million marathon results shows that runners who run the first half faster than the second lose seven to ten minutes on average compared to an evenly paced race.

Training also hangs on the goal time: race-pace blocks, threshold runs and the pace during tapering all follow the planned race pace. Anyone planning around a fantasy goal time spends weeks turning the wrong dial.

The Riegel formula: the classic

The best-known method comes from American researcher Pete Riegel (1977):

T2 = T1 × (D2 ÷ D1)^1.06

T1 is your best time over distance D1, T2 the predicted time over D2. The fatigue exponent of 1.06 expresses that pace drops by roughly six percent per doubling of distance. An example: you run 10K in 50:00 (5:00/km) and want your half marathon time. The distance factor is 21.1 ÷ 10 = 2.11; raised to the power of 1.06 that gives roughly 2.20. Prediction: 50:00 × 2.20 = 110 minutes, or about 1:50.

The formula works so well because it was calibrated on real race data from thousands of runners — from 5K to the marathon. It is the basis of virtually every online calculator and of the prediction tables found in training plans.

Worked example: from 10K to the marathon

A look at the common conversions shows how the formula behaves. Starting point: 10K in 50:00 from a real race on a flat course.

• 5K: 50:00 × (5 ÷ 10)^1.06 ≈ 23:58 — the shorter distance allows about 4:47/km.
• Half marathon: ≈ 1:50:20, a pace of 5:14/km.
• Marathon: 50:00 × (42.2 ÷ 10)^1.06 ≈ 3:42, a pace of 5:16/km.

Notably, the predicted pace barely drops from the half marathon to the marathon — and that is exactly where the trap lies. The formula assumes you are fully trained for the target distance. Someone training on a 10K base who "just runs" a marathon will miss the 3:42 by 15 to 25 minutes. Someone who completes a solid 16-week marathon plan with long runs beyond 30 kilometres will often hit the prediction to the minute.

When the formula lies

• Wrong reference. A training best on a flat bike path with a tailwind is not a race result. Only use times from real races or honest time trials on comparable terrain.
• Too big a jump. Extrapolating from 5K to the marathon works poorly. Rule of thumb: the target distance should be at most four times the reference distance. For the marathon, a half marathon time is the best basis.
• Missing specificity. The prediction assumes specific training — for the marathon that means long runs and marathon-pace blocks; for a gran fondo, long aerobic rides.
• Environmental conditions. Heat above 18 degrees, wind, elevation gain: everything the formula does not know costs a real two to five percent.

Alternative methods: critical speed and test races

For more precision, use the critical speed approach: from two all-out time trials of three and twelve minutes you calculate the speed you could theoretically hold indefinitely. Your realistic race pace sits at 90 to 95 percent of that — the longer the distance, the closer to 90. The advantage: critical speed measures your current threshold performance directly, without extrapolating across distances.

The most practical method remains the test race: a 10K race four to six weeks before a half marathon, a half marathon eight weeks before the marathon. Test races deliver not just a number but also the experience of what race pace feels like under competitive stress — something no formula can model.

From goal time to race pace

The predicted goal time is only the beginning — from it you derive your per-kilometre pace and from that your pacing strategy for the race. For most recreational runners, an even pace or a slight negative split is the safest choice. Take the formula's prediction, calculate your race pace and test it in training: three to four weeks before the race you should be able to run twelve to fifteen kilometres at marathon pace without your heart rate climbing into threshold territory. If you cannot, the goal time is too ambitious — better to correct it now than at kilometre 30.

A proven approach is the A-B-C goal: A is your dream time if everything goes perfectly; B is the Riegel prediction; C is a time you would still be happy with on a difficult day. This anchors the prediction mentally without hanging the entire race on a single number.

The five most common goal-time mistakes

• Wish instead of calculation. "Sub-4 hours" sounds better than 4:07 — but the body does not care about round numbers. Plan with what your data says.
• Outdated reference. A personal best from three years ago does not count. The reference time should be no older than three to six months and match your current training state.
• Prediction as starting pace. Using one hundred percent of the predicted time as your pace target leaves no reserve for weather, course profile or an average day. Subtract one to two percent.
• Overestimating the test race. A top time in a test race after a full taper is not transferable if no taper is planned before the main race — plan realistically.
• Only one number in your head. Without B and C goals, every small wobble during the race becomes a mental crisis. Flexible goals keep motivation alive to the finish.

How Peakora derives your goal time

Peakora does not calculate with a rigid formula but with your data: the engine analyses your logged sessions, detects your current performance level and derives realistic pace corridors for every workout — including the race pace for your A-race. Because the prediction updates with every session you log, you can see week by week whether you are on track. That makes goal-time planning especially valuable in marathon preparation, where a wrong pace target can undo twelve weeks of work.

Frequently asked questions about race time prediction

How accurate is the Riegel formula?

For endurance events from 5K to the marathon, the Riegel formula is typically accurate within two to three percent for well-trained runners. The reference time must come from an all-out race or time trial, and the target distance should be no more than about four times the reference distance.

Can I calculate my marathon time from my 10K time?

Yes, but with a discount: the Riegel formula predicts about 3:42 for the marathon from a 50-minute 10K. Without marathon-specific training including long runs, 3:50 to 4:00 is more realistic. The formula assumes you train specifically for the target distance.

Which is better: the Riegel formula or critical speed?

For distances up to the half marathon, critical speed is more precise because it measures your actual threshold performance instead of extrapolating. For the marathon, the Riegel formula based on a recent half marathon time gives more practical values. Combining both methods is ideal.

Why was my race prediction wrong?

The most common reasons are heat, a hilly course, starting too fast and poor fueling. The formula only knows your fitness, not race-day conditions. Plan two to five percent slower when temperatures exceed 18 degrees Celsius or the course is hilly.