Use case · 1.5 km · 40 km · 10 km

Olympic-distance regular

Four to eight races a season. You want each one to be a little faster than the last.

Start free trial All use cases

12 Apr 2026 · Olympic (Standard) · sampleMossel Bay Triathlon

Race detail

Swim29:05

T12:10

Bike1:13:48

T21:04

Run49:37

T1 suggested 2:10 from Strava timestampsT2 suggested 1:04

Leg	Time	Category place
Swim	0:29:05	22 / 61
Bike	1:13:48	11 / 61
Run	0:49:37	17 / 61
Overall	2:35:44	14 / 61

The situation

You race often and you know the courses. Your results are scattered across three timing websites, and you want to see the season as a whole, not as a list of activities.

The problem

Official results are scattered across FinishTime and PeakTiming.
Transitions are guessed, not measured.
Per-leg placing is buried in results PDFs.

The race

What the day adds up to

The goal, split by leg. Every number on this page comes back to these five.

Olympic (Standard) · result · sampleGoal 2:35:44

Swim

1.5 km0:29:05

0:02:10

Bike

40 km1:13:48

0:01:04

Run

10 km0:49:37

The screens that answer it

Results finderFinds your official results and shows you what would change before anything is saved.RacesPer-leg placing for every triathlon, T1 and T2 from your Strava timestamps.RecordsPBs per course and distance, with the season in one view.

Walk-through

On sample data

A short run through how it plays out. The numbers are illustrative.

Race 1Results finder matches your result. Five fields update after you confirm.
Race 3T2 suggested at 0:58 from Strava timestamps, 22 seconds faster than race 1.
Race 5Run leg placing climbs from 19th to 11th in category.
SeasonFive races, one course PB, and a clear picture of which leg improved.

After every session