Triathlon data project · August 6, 2026 · Alpe d’Huez
Triathlon L — every split of every athlete
Swim 2.2 km · Bike 118 km · Run 20 km. The long one: 2.2 km in the Lac du Verney, a 118 km bike leg over the Grand Serre and the Col d'Ornon, the 21 hairpins of the Alpe, then three laps of a run at 1,800 m. This explorer indexes the full timing data — 1,559 ranked finishers timed on 22 mats, rank at every one of them, leg-by-leg rank flow, and a page per athlete.
Every athlete has a page: leg splits, checkpoint ranks, times vs. the field — and the second of the livestream where they cross the mat.
1,559
Ranked finishers
1,942 entered, 1,908 started
5:33:41
Winner's time
Thomas STEGER
6:13:00
First woman
Alanis SIFFERT
9:03:55
Median finisher
223 women classified
The front of the race 🏊 🚴 🏃
0:00:00
Thomas STEGER0 kmÉmile BLONDEL-HERMANT0 kmLouis RICHARD0 kmClement GRANDY0 kmPierre DUPUY0 km
Athletes move along the real course profile, positions interpolated between the timing mats from their split times.
The five fastest, at their own recorded splits — watch them come out of the water, spread out over the cols and close up again on the run. The badge follows whichever discipline they are in. The bike leg is the organiser’s own GPX. The swim and the run are drawn flat — at the lake’s surface and at resort altitude — because neither has a published profile, and inventing undulation would be decoration, not data.
What would it take? 🎯
Pick a place — overall or in your category — and this shows the race that produced it in 2026: the finish time, the split on every leg, and roughly what you would have to push up the Alpe to get there. Then tell it what you can run, and it works out what is left for the bike.
6:56:05
the time that got you there in 2026
3.4 W/kg
on the Alpe · ≈236 W at 70 kg
1:09:05
for the 13.4 km climb (948 m/h)
Swim
T1
Bike
T2
Run
33:32
2:51
4:47:46
2:05
1:29:514:53/km
…but I know my run. If I run the 18.42 km ats/km (5:00/km), then the bike has to be:
4:45:3125.6 km/h over 121.8 km
Swim and transitions held at the 100th-place medians above.
The times are what Triathlon L athletes around that place actually did in 2026 — the median of everyone within five places — not a model of how the race should be paced. The watts are the one estimate: VAM ÷ (200 + 10 × gradient) over the climb’s 1091 m at 8.1%, which ignores wind, drafting and how much you left on the bike before you got there. Treat it as a ballpark, and remember 2027 will be a different day.
Leg by leg: who was where, when
The order at the finish has very little to do with the order out of the water. Each line is one of the top 10 finishers; its height is their overall rank at the mat that closes each leg. Thomas STEGER came out of the water in 19th place and still won. The x axis is the sequence of legs, not distance — most checkpoint distances on this course are interpolated, and a distance axis would quietly turn an estimate into a fact.
Who won each leg
Each leg is timed between two mats and ranked on its own. Winning a leg and winning the race are different jobs.
The Montée de l’Alpe d’Huez, 13.4 km from the foot to the line at the top, is a timed segment in its own right — and one of the few spans on this course where both mats have a real, measured distance, so the km/h below are honest rather than interpolated. 1,688 athletes were timed on it; the median took 1:32:35.
This race has a second timed climb: Montée du Grand Serre. Its distance is interpolated, so its leaderboard is ranked on time only.
The transitions
T1 and T2 are timed legs like any other, and in a field this deep they decide real places. The spread is enormous: on this course the gap between the fastest and the median transition is bigger than most people’s margin over the athlete in front.
The median athlete spends 5:12 here — 4:43 more than the fastest. No km/h: it is a few dozen metres of running in bike shoes, and the distance is interpolated anyway.
The median athlete spends 3:47 here — 2:41 more than the fastest. No km/h: it is a few dozen metres of running in bike shoes, and the distance is interpolated anyway.
Finish times in 5-minute buckets, from 5:33:41 to 12:10:00 — the median finisher took 9:03:55.
Counts everyone with a finish time, which includes the few athletes who crossed the line but were not classified — so the bars total slightly more than the 1,559 ranked finishers.
≈ = the length is not the timing provider’s own measurement. The timing provider publishes no distances. Five checkpoints per race are pinned from the split tables (they expose km/h alongside the time). On the long course the rest are read off the official course GPX — summits, the valley low point, the half-height of a climb — and the three villages the route only passes near are interpolated to ±1–2 km. Anything not measured by the provider is marked ≈, and speeds are shown only where both ends of a segment are pinned.
Rankings at every mat
The course had 22 timing mats — who led the race at each one, and how the field spread out. Mats occasionally miss an athlete, which is why some athlete pages show “mat missed” on a leg.
2 segment times in this race are physically implausible for that athlete’s level in the rest of the race — almost certainly a phantom mat read. They stay visible and are excluded from every ranking and stat on this site.
Times that are physically implausible for that athlete’s level are kept visible but excluded from the rankings here. Two of them are ranked by chronorace, the official timekeeper: Bart PROVOST is their Montée de l’Alpe winner in the Duathlon, and Bruno PERRIN their fastest bike in Triathlon M. Neither finished their race, and both times would be near-professional. We hold them back; the official results do not. It means “not credible”, not “cheated”.
How to read these numbers
1,559 finishers, 1,942 entrants. Athletes who did not start, abandoned, or were ranked by how far they got are all in the dataset — with no rank and no finish time — and are never counted as finishers. You will meet them in the search box and on checkpoint pages, marked with their status.
Distances marked ≈ are interpolated. The timing provider publishes no distances. Five checkpoints per race are pinned from the split tables (they expose km/h alongside the time). On the long course the rest are read off the official course GPX — summits, the valley low point, the half-height of a climb — and the three villages the route only passes near are interpolated to ±1–2 km. Anything not measured by the provider is marked ≈, and speeds are shown only where both ends of a segment are pinned.
Find yourself in the livestream
The timekeeper indexed the event’s YouTube streams against every chip read, so each athlete page carries Swim and Bike links that open at the exact second they crossed the mat — plus their photo tag and official diploma. Search your name above.
🐛 Something looks off? Wrong time, missing athlete, a leg that doesn’t add up — this is a one-person side project on top of raw timing data, and reports make it better. Email me.
About this project. Timing data from the official race timekeeping (chronorace), fetched once after the event and republished here with per-leg segment times, recomputed leaderboards and per-athlete pages the official results don’t offer. All three races of the weekend →