About Race Replay
Why this exists and how it came to be.
The problem
Race results pages show you your chip time and your overall rank, but they don't tell you what actually happened on course. When everyone starts at a different time, finishing rank doesn't reflect the physical experience of racing.
Did you pass 50 people on the bike leg of a triathlon? Did someone come flying past you in the last 5k? Standard results have no answer. Race Replay does.
How it works
By anchoring each athlete's split times to their personal start time, we compute an absolute clock position at every timing checkpoint. Comparing those positions leg-by-leg reveals every physical pass — who moved forward, who got caught, and by how much.
The algorithm self-checks: every pass gained by one athlete must correspond to a pass conceded by another. If the totals don't balance, something is wrong with the data and we surface that rather than show you misleading numbers.
Who built this
Race Replay is a project by Cloudgate Studios. It started as a personal tool to make sense of triathlon results, and grew into something worth sharing with the broader racing community.
The project is open source. If you want to see how it works under the hood, report a bug, or add support for a new race series, the code is on GitHub.
