Triathlon Time Calculator, Explained

After reading this you can add up the five parts of any triathlon by hand, see which leg holds most of your finishing time, and avoid the pacing errors that make race-day predictions too optimistic.

A triathlon time is not one number, it is five numbers stacked on top of each other: the swim, the first transition (T1), the bike, the second transition (T2), and the run. The calculator turns your planned swim pace, bike speed and run pace into a total and shows each leg's share.

Here is the hook. Take a common Olympic-distance plan: swim 1500 m at 2:05 per 100 m, bike 40 km at 30 km/h, run 10 km at 5:30 per km, with a 3-minute T1 and a 2-minute T2. Most people guess the bike dominates. The bike does take the most clock time, about 80 minutes, but the run at 55 minutes and the swim at 31 minutes together are larger. Knowing those shares tells you where a training hour actually buys you time.

What the tool does and when to use it

The calculator sums five durations. You give it a course (or a custom set of distances), a pace or speed for each of the three sports, and two transition times. It returns the total and the percentage each leg contributes.

Use it when you want a target time from paces you can already hold, or when you want to test a "what if" (what does dropping bike speed from 30 to 32 km/h save?). It is a planning and pacing model, not a physiology model.

The tool assumes you hold each pace for the full leg. It does not model fatigue, so a run pace entered at your fresh 10K speed will produce a total that is faster than you will really run off the bike. Feed it realistic race paces, not personal bests.

Do not use it to compare athletes of different ages or to convert a pool time to open water without adjusting the pace yourself. For those, see the related tools near the end.

The formula and the intuition behind it

Total time is a plain sum. The only trick is keeping units straight: swim pace is time per 100 m, run pace is time per km, and bike is a speed rather than a pace.

T = t_1 + t_2 + p_{sw} \cdot \frac{d_{sw}}{100} + \frac{d_{bk}}{v_{bk}} + p_{rn} \cdot d_{rn}

Here T is total time, t_1 and t_2 are the two transition times, p_{sw} is swim pace in seconds per 100 m, d_{sw} is swim distance in metres, v_{bk} is bike speed in km/h, d_{bk} is bike distance in km, p_{rn} is run pace in seconds per km, and d_{rn} is run distance in km. Convert everything to seconds first, then read the result back as h:mm:ss.

The intuition: a pace multiplies by distance, a speed divides into distance. Swim pace of 2:05 is 125 seconds per 100 m, so 1500 m costs 125 \times 15 = 1875 seconds. Bike speed of 30 km/h means 40 km takes 40 / 30 = 1.333 hours, which is 4800 seconds. Run pace of 5:30 is 330 seconds per km, so 10 km costs 330 \times 10 = 3300 seconds.

A worked example with the demo numbers

Olympic distance at moderate paces

Reproduce the demo: 1500 m swim at 2:05/100 m, 40 km bike at 30 km/h, 10 km run at 5:30/km, T1 of 3:00, T2 of 2:00.

Swim: 2:05 = 125 s per 100 m. 125 \times (1500/100) = 1875 s = 31:15.
T1: 3:00 = 180 s.
Bike: 40 / 30 = 1.3333 h = 4800 s = 1:20:00.
T2: 2:00 = 120 s.
Run: 5:30 = 330 s per km. 330 \times 10 = 3300 s = 55:00.
Total: 1875 + 180 + 4800 + 120 + 3300 = 10275 s.

10275 seconds is 2 hours, 51 minutes, 15 seconds (10275 / 3600 = 2.854 h; the remainder 0.854 h is 51.25 min). So the finishing time is 2:51:15.

The leg shares follow by dividing each duration by 10275. The bike is 4800/10275 = 46.7\%, the run is 3300/10275 = 32.1\%, the swim is 1875/10275 = 18.2\%, and the two transitions together are 300/10275 = 2.9\%.

The bike is the largest single block at 80 minutes, but swim plus run together (86.25 minutes) exceed it.

Reading the leg shares

The share tells you where a percentage improvement pays off most. A 3% speed gain on the bike (30 to 30.9 km/h) saves about 140 seconds. A 3% pace gain on the run (5:30 to 5:20 per km) saves about 100 seconds. A 3% swim gain saves about 56 seconds. The bike returns the most because it is the biggest time block, not because the sport is special.

Transitions look trivial at 2.9% of an Olympic race, and for a fit age-grouper they often are. But the share grows for short races. In a sprint that finishes near 70 minutes, a sloppy 5-minute combined transition is over 7% of the day, larger than most people's realistic swim gains.

Rank your legs by share, then by how trainable they are. A leg with a large share and a lot of room to improve (often the bike for runners, the run for swimmers) is where your next block of training buys the most seconds.

Explore the trade-off yourself

The instructive thing a static chart cannot show is how the total moves when you change one leg while the others stay fixed. Slide the bike speed and watch both the total and the leg shares respond.

Common mistakes

The four errors below account for most of the gap between a calculated time and a real finish.

Pool pace for an open-water swim: Open water is usually 5 to 10 s per 100 m slower because of sighting, chop and no wall push-offs. A 2:05 pool swimmer entering 2:05 will likely swim 2:10 to 2:15, adding 45 to 90 seconds over 1500 m.
Fresh run pace: Running off the bike costs 10 to 20 s per km at first. A 5:30 open runner may start the 10 km closer to 5:45, adding 90 to 150 seconds.
Two-minute transitions everywhere: Big races have long carpeted runs between the water, the racks and the mount line. Some venues add 2 to 4 minutes per transition beyond the quick T1 you practise.
Bike speed from a flat solo ride: Course hills, wind and drafting rules change your real average. A speed that holds on a flat time trial can drop 2 to 3 km/h on a rolling course.

Stack these and the demo 2:51:15 can realistically become 2:58 to 3:03. That is not a flaw in the arithmetic. It is the difference between the paces you enter and the paces the day allows.

Related tools

Estimate the paces before you feed them in. Use the Swim Pace & CSS Calculator to turn a 400/200 m test into a sustainable swim pace, and the Race Time Predictor or VDOT Running Calculator to set a run pace from a recent race. To plan the run leg once you have a target, the Race Split Calculator builds a per-km table.

For race-day conditions, the Heat & Altitude Pace Adjuster corrects your run pace for weather, and the Marathon Fueling Calculator and Sweat Rate Calculator plan carbs and fluids for the long distances. To compare a finish across ages, use the Age Grading Calculator, and to convert treadmill work in training, the Treadmill Incline Converter.

Frequently asked questions

How accurate is the predicted triathlon time?

The sum itself is exact for the paces you enter. The error lives entirely in your pace estimates. If your swim, bike and run paces are each within 3%, your total is within roughly 3%, so a 3-hour prediction sits in a window of about 5 to 6 minutes either way.

Why does the bike take so much of the total?

Because it is the longest leg by time. At Olympic distance the bike is 40 km at 30 km/h, which is 80 minutes, more clock time than the swim and run individually. Its 46.7% share comes from duration, not from any special weighting.

Should I use my pool pace or open-water pace?

Use an open-water pace, which is typically 5 to 10 s per 100 m slower than your pool pace. Over 1500 m that difference is 75 to 150 seconds, enough to move your predicted total by more than a minute.

What transition time should I plan for?

A practised age-grouper often runs T1 and T2 in 1 to 3 minutes each. Large races with long change areas can push each transition to 4 or 5 minutes. Check the venue map rather than assuming the 2 to 3 minute defaults.

Can I model a custom or non-standard course?

Yes. Choose the custom option and enter your own swim metres, bike km and run km. The same formula applies: pace times distance for swim and run, distance divided by speed for the bike, plus both transitions.

This is an educational estimate for sport and training purposes. It is not professional coaching or medical advice.

Try it yourself in the tool