Understanding Strava Leaderboards: KOM, Top 10 and Your Rank
Before hunting a KOM you should know which time you are actually racing — and how meaningful that time is.
How the leaderboard is built
Every activity matching the segment geometry is timed and ranked. There are no categories for bike type, weather or wind direction — the fastest time wins, whatever the circumstances.
Why top times can look unreachable
The reasons are usually mundane: a storm day with perfect tailwind, a ride in a group's draft, a motor-paced effort, a race with time-trial pacing, or faulty GPS data. A single extremely fast time is therefore a poor reference for your own goal.
Use a realistic reference
Look at positions 5 to 20 instead of only the KOM. Those times were mostly set in normal conditions and describe the achievable level far better.
- KOM time: upper bound, often with special conditions
- Top 10 time: ambitious but achievable
- Median of the top 50: a good benchmark for your current form
Your rank as a model input
Knowing that you sit 28th of 1200 lets a model estimate the time distribution far more realistically than the KOM time alone. That is why KomPredict lets you enter your current rank — ranking probabilities become much more meaningful.
In short
Benchmark against the top 10, not an outlier — and enter your rank so probabilities make sense.
Frequently asked questions
Why is my rank not fetched automatically?
Strava only exposes leaderboard data through its interface in a limited way. So you enter your rank once yourself, or open the segment on Strava.
Can suspicious times be reported?
Yes, Strava lets you flag clearly faulty entries such as car rides. Not every case gets processed.