Reading the leaderboard¶
The public leaderboard is what riders, spectators, and you yourself see at the event's URL. It's the most visible artefact your event produces. This page covers what it shows, how to read it, and what to expect during a live event.
What's on the page¶
The event's public page contains:
- the event title, dates, and venue at the top
- the reference run — playable so anyone can see the track
- the leaderboard — every run on the event, ranked
- a way for riders to upload their own run
The page is open — anyone with the link or QR can view it. No account, no install required. Riders only need the app to upload.
How runs are ranked¶
Runs are ranked by total time across the track, measured from the reference run's start split to the reference run's finish split.
A run only appears on the leaderboard once it has finished processing and its splits have been confirmed (either manually by the rider or via the predicted splits the rider accepted).
If a run is mid-processing, you'll see it as pending; once processing finishes, it slots into its position on the board.
Per-split times¶
For each run, the leaderboard surfaces:
- total time — the headline number
- per-split times — at each intermediate split the reference defines
- delta to the reference — how the run compares to the canonical pass at each split and overall
If you want a deeper read on what those numbers mean, see Time delta.
What the leaderboard does not show¶
A few honest limits, worth knowing before riders ask:
- it's not chip-timing. Runs are timed from video against a reference, not from a transponder. For most community events this is great; for sanctioned timing, it isn't a substitute.
- it doesn't deduplicate runs. If a rider uploads three attempts, all three appear on the leaderboard at their respective times. The rider's best run is the one that ranks highest.
- late uploads stop landing once the event window closes. The page stays live with the final standings, but new runs after the end time don't change the result.
Riders' identities¶
Each run is labelled with the rider in the video — the athlete name tagged on the run. The uploader's account name is not shown publicly.
If a rider's name is wrong on the leaderboard, the uploader can re-tag the run and the page updates. See How riders join for the most common cause (one account uploading for many riders without setting the athlete tag).
During a live event¶
Expect the leaderboard to update every few minutes as runs upload and finish processing. On a busy race day with simultaneous uploads, processing can queue up — runs still finish, just a little later than the moment of upload.
A few practical things that help during a live event:
- a screen at the finish showing the leaderboard URL full-screen is the highest-impact spectator experience
- a QR poster at the start gate so riders join while warming up
- the WhatsApp group as the channel for "my run isn't showing yet" questions — usually it just needs another minute
If the leaderboard appears stuck — no new runs landing, processing seems frozen across the board — contact us during the event and we'll dig in.
After the event¶
Once the event window ends, the leaderboard freezes. The public page stays up with the final standings until you ask us to take it down. If you're running a series, each round has its own page and its own final standings.