Leaderboard¶
A leaderboard is the ranked list of runs in a track session or a public event. It's the most direct answer to "who was fastest?" — and, with splits, "who was fastest where?".
What the leaderboard ranks¶
Every run in the session or event that has finished processing and has confirmed splits appears on the leaderboard, ranked by total time. Total time is measured from the start split to the finish split — the same window on every run, defined by the reference run.
Within a session or event, all runs share the same start and finish definition, so total times are directly comparable.
What's on each row¶
Each leaderboard row typically shows:
- the rank
- the rider in the video — the athlete name on the run, not the uploader's account
- the total time
- per-split times at each intermediate split
- the time delta to the reference at the finish
Tapping into a row opens that run's full comparison view, with the continuous time-delta curve.
Multiple runs by the same rider¶
A rider with three attempts has three rows on the leaderboard, each at its own rank. The rider's "best run" is whichever of theirs ranks highest.
The leaderboard does not deduplicate by athlete. This is deliberate — it means you can see how a rider's pace progressed across the session, not just their personal best.
Leaderboards across contexts¶
- solo session — every run is the same rider's, so the leaderboard becomes a personal-best chart over time
- team session — runs from every team member, ranked together against the team's reference
- public event — runs from every rider on the event, ranked against the event's reference, visible on the open web
The mechanics are the same in all three. The audience is what changes.
When a run doesn't appear¶
A run is missing from the leaderboard when:
- it's still uploading or processing
- its splits haven't been confirmed yet
- it was uploaded outside the event window (for public events)
Once those resolve, the run lands on the board at its rightful rank.
Why the order can change¶
The leaderboard recalculates when:
- the reference run is changed — splits are re-predicted, ranks may shift slightly
- a new run is uploaded and finishes processing — it slots into its rank
- a confirmed split is edited — the affected run's split times change, and its rank may move
The numbers are derived, not stored as a frozen ranking. Anything that changes the inputs changes the output.