How is triathlon finish time calculated?

Add swim time, T1, bike time, T2 and run time. A 1500 m swim at 2:00 per 100 m takes 30 minutes; 40 km at 40 km/h takes one hour; 10 km at 5:00 per km takes 50 minutes. With two-minute T1 and one-minute T2, the total is 2:23:00.

What happens when I change units or input mode?

The planner converts distances and pace or speed using exact unit ratios, including 1609.344 metres per mile. Switching between time, pace and speed preserves the leg duration. Rounded displayed fields retain exact values internally until you edit them.

Are the distance presets official event distances?

They are editable conveniences. Sprint uses 750 m, 20 km and 5 km; Standard uses 1500 m, 40 km and 10 km; Middle uses 1900 m, 90 km and 21.1 km; Long uses 3800 m, 180 km and 42.2 km. Event distances vary. Presets change distances only and retain your time, pace or speed assumptions.

How do I compare scenarios?

Save a snapshot, change one or more assumptions, and save another. Up to 50 scenarios remain in page memory. Load copy restores a snapshot for editing without changing the saved row; remove and one-level undo manage the list. CSV and print include saved snapshots, or the current scenario when the list is empty.

Why is my finish time incomplete?

Each leg needs a positive distance and time, pace or speed. Both transitions must be supplied but may be zero. Times accept seconds, m:ss or h:mm:ss. The target is optional and only compares against the calculated finish; it does not adjust your inputs.

Does this predict race performance?

No. It adds constant-pace assumptions supplied by you. It does not model weather, elevation, fatigue or individual performance, and provides no training or safe-exertion recommendation. Scenarios are not automatically saved; export before leaving the page.

Triathlon Time Planner

Build a finish-time scenario from your own distances and constant pace, speed or time assumptions. Add both transitions, inspect cumulative splits, and save scenarios to compare changes.

Build a finish-time scenario

Scenario label

Choose distances, then enter one time, pace or speed assumption per leg. Switching input mode or units converts the existing values and preserves duration. Editing a number replaces that value.

Presets change distances only: Sprint: 750 m · 20 km · 5 km; Standard: 1500 m · 40 km · 10 km; Middle distance: 1900 m · 90 km · 21.1 km; Long distance: 3800 m · 180 km · 42.2 km. Event distances vary; every distance is editable.

Swim

DistanceDistance unitsInput modePace per 100 m

Time: 30:00.000
Pace: 2:00.000 / 100 m
Speed: 3000 m/h

Bike

DistanceDistance unitsInput modeSpeed (km/h)

Time: 1:00:00.000
Pace: 1:30.000 / km
Speed: 40 km/h

Run

DistanceDistance unitsInput modePace per km

Time: 50:00.000
Pace: 5:00.000 / km
Speed: 12 km/h

T1: swim to bikeT2: bike to runTarget finish time (optional)

Times accept seconds, m:ss or h:mm:ss, with up to three decimal places in seconds. Transitions may be zero; blank leg or transition inputs keep the total incomplete. Calculations retain exact fractions behind converted fields; displayed times round to milliseconds and speeds to six decimals.

Calculated finish time

2:23:00.000

7:00.000 before target · target 2:30:00.000

Cumulative timeline
Segment	Duration	Elapsed finish
Swim	30:00.000	30:00.000
T1	2:00.000	32:00.000
Bike	1:00:00.000	1:32:00.000
T2	1:00.000	1:33:00.000
Run	50:00.000	2:23:00.000

Compare saved scenarios (0/50)

Save a snapshot, edit an assumption, then save again to compare. Loading creates an editable copy. Scenarios stay in page memory only; export before leaving. Up to 50 snapshots; remove a row to make room.

Exports include the current valid scenario. CSV includes inputs, derived values, cumulative splits and exact metre/millisecond fractions. Print puts each scenario on its own page.

Constant-pace arithmetic from supplied assumptions, not a race-performance prediction or a training/safe-exertion recommendation. No weather or elevation adjustment. Distance presets are editable conveniences; event distances can vary. Inputs remain in your browser.

Common questions

How is triathlon finish time calculated?: Add swim time, T1, bike time, T2 and run time. A 1500 m swim at 2:00 per 100 m takes 30 minutes; 40 km at 40 km/h takes one hour; 10 km at 5:00 per km takes 50 minutes. With two-minute T1 and one-minute T2, the total is 2:23:00.
What happens when I change units or input mode?: The planner converts distances and pace or speed using exact unit ratios, including 1609.344 metres per mile. Switching between time, pace and speed preserves the leg duration. Rounded displayed fields retain exact values internally until you edit them.
Are the distance presets official event distances?: They are editable conveniences. Sprint uses 750 m, 20 km and 5 km; Standard uses 1500 m, 40 km and 10 km; Middle uses 1900 m, 90 km and 21.1 km; Long uses 3800 m, 180 km and 42.2 km. Event distances vary. Presets change distances only and retain your time, pace or speed assumptions.
How do I compare scenarios?: Save a snapshot, change one or more assumptions, and save another. Up to 50 scenarios remain in page memory. Load copy restores a snapshot for editing without changing the saved row; remove and one-level undo manage the list. CSV and print include saved snapshots, or the current scenario when the list is empty.
Why is my finish time incomplete?: Each leg needs a positive distance and time, pace or speed. Both transitions must be supplied but may be zero. Times accept seconds, m:ss or h:mm:ss. The target is optional and only compares against the calculated finish; it does not adjust your inputs.
Does this predict race performance?: No. It adds constant-pace assumptions supplied by you. It does not model weather, elevation, fatigue or individual performance, and provides no training or safe-exertion recommendation. Scenarios are not automatically saved; export before leaving the page.