🏊 Triathlon Time Estimator

How to Use This Triathlon Time Estimator

Add up honest paces for each leg and the estimator builds your finish time. It is the reality check every triathlete needs before race week: the number it gives is usually slower than the number in your head, and it is usually right.

The Math

Each leg is distance divided by pace, converted to seconds, then summed. Olympic defaults: swim 1500/100 x 120 s = 1800 s = 30:00; bike 40/30 x 3600 = 4800 s = 1:20:00; run 10 x 330 = 3300 s = 55:00; transitions 5:00; total 10,200 s = 2:50:00. The estimator assumes you actually hold those paces back to back, which is the optimistic part: the bike always costs the run something, and open water always costs the swim something. Treat the result as a good-day estimate.

Worked Example

Select Olympic, swim pace 120 s/100m, bike 30 km/h, run 330 s/km, transitions 5 min. Swim = 15 x 120 = 1800 s. Bike = 40/30 = 1.333 h = 4800 s. Run = 10 x 330 = 3300 s. Transitions = 300 s. Total = 1800+4800+3300+300 = 10,200 s = 2:50:00. A sprint with the same paces and 4 min transitions: swim 900, bike 2400, run 1650, plus 240 = 5190 s = 1:26:30. Verify both in the calculator.

Where Estimates Go Wrong

Three classic errors: using pool sprint pace instead of sustainable open-water pace, using group-ride bike speed instead of solo speed, and using fresh 10K run pace instead of off-the-bike pace. Each error compounds across the total. The honest inputs are your critical swim speed plus 5 percent, your solo training ride speed minus 1-2 km/h for race-day caution, and your easy run pace plus 15-30 s/km. Enter those and the estimate becomes a plan you can actually execute.

From Estimate to Race Plan

Once the total looks right, convert each split into a pacing band: swim at controlled effort (the swim is too short to win, long enough to ruin the day), bike at the wattage or heart rate you trained, run the first third conservatively. Write the splits on your arm. Practice transitions twice before race week: two smooth minutes beat two panicked ones. And build a 5 percent buffer into the goal; the estimate assumes a good day, and race days are rarely perfect.

Second worked example: 70.3 with honest paces

Select 70.3, swim pace 120 s/100m, bike 28 km/h, run 360 s/km, transitions 8 min. Swim = 19 x 120 = 2280 s = 38:00. Bike = 90/28 x 3600 = 11,571.4 s = 3:12:51. Run = 21.1 x 360 = 7596 s = 2:06:36. Transitions = 480 s. Total = 2280 + 11,571.4 + 7596 + 480 = 21,927.4 s = 6:05:27. Compare with the Olympic example at 2:50:00: the 70.3 takes more than twice as long despite being roughly twice the distance, because pace fades as distance grows. Enter these numbers in the estimator and verify the total, then add 5 percent for open water and race-day friction: 21,927 x 1.05 = 23,024 s = 6:23:44, a more honest race-day target.

Where the time goes: sprint vs Ironman

The legs trade shares as distance grows. In a sprint, a mid-pack athlete might swim 15 minutes, bike 35, run 25: the bike is about 45 percent of the total. In an Ironman, the same athlete swims 75 minutes, bikes 390, runs 300: the bike is over 50 percent. Two lessons follow. First, bike fitness buys the most time at every distance, which is why triathletes ride more hours than they swim and run combined. Second, the run matters disproportionately at long distance: it is where the race is decided, because everyone can ride the bike leg but only the well-paced can run the marathon. Budget training hours accordingly, and never sacrifice the long run to squeeze in another swim.

Common estimation mistakes

Mistake one is the wetsuit fantasy: entering pool pace without the 5 to 15 percent open-water penalty, then wondering why the swim split missed by 8 minutes. Mistake two is group-ride bike speed. Sitting in a pack at 32 km/h is not a solo 32; enter your solo training speed minus 1 to 2 km/h. Mistake three is fresh-leg run pace. Your open 10K pace is meaningless after 90 km of riding; add 15 to 30 seconds per km for the off-the-bike reality. Every one of these errors points the same direction, optimistic, which is why the estimator's total usually looks fast until you feed it honest inputs.

For informational purposes only, not medical advice. Consult a healthcare professional.

The Transition Tax: Where Beginners Bleed Minutes

New triathletes obsess over bike speed and ignore the two transitions, which is exactly backward for where their minutes go. A practiced age-grouper does T1 in about 90 seconds and T2 in a minute; a beginner fumbling with socks, a GPS watch, and a jacket can spend 4 to 5 minutes per transition. That is 6 to 8 minutes of free time sitting on the table, equivalent to gaining roughly 1 mph on the bike leg without pedaling any harder.

The fixes are cheap and unglamorous. Lay out the transition area in order of use the night before and walk through it mentally twice. Elastic laces turn running shoes into slip-ons. Practice the wetsuit strip once in training so race morning is not the first attempt. None of this shows up in a pace chart, and all of it shows up in the finishing time. Transitions are the only part of triathlon where practice has no fitness prerequisite.