We’re Improving Leaderboard Accuracy ✅

[mal]

Good news! We’re updating our algorithms to make leaderboards more credible, and taking steps to proactively prevent suspicious efforts from appearing on leaderboards – so you can trust that the results you see are accurate. We're withholding from leaderboards any activities that appear incorrectly labeled (e.g. a bike ride getting uploaded as a run) or have faulty GPS data.

With these and other ongoing changes, we can better ensure your efforts will get the ranking they deserve and you can trust that the CR, KOM or QOM (plus all the other times on the leaderboard) are the real deal. These changes will be for all activities moving forward – we can’t yet capture past activities. And of course, you can still report an activity if you think there’s one the algorithm missed. Learn more about that here.

This is a big undertaking – we saw around 26,000 1-mile running splits that would have been faster than the world record last week! – and the work will be ongoing. Here’s how we’re committing to cleaning up leaderboards right now:

The Details 📝

✔️ There’s a new threshold for flagging: Activities with too much erroneous data will be automatically flagged – which means all segment efforts from those activities will be withheld from leaderboards.
✔️ We’re doubling down on catching bike rides (or downhill ski runs, car rides, etc.) marked as runs with new run-specific parameters that will flag activities based on their distance and pace data.

[SabtainSaleem]

It’s great to see Strava focusing on improving leaderboard accuracy! Accurate data is crucial for keeping the competition fair and motivating everyone to push their limits. These enhancements will definitely help athletes trust the rankings more, leading to a better overall experience. Looking forward to seeing the positive impact this has on the community! Keep up the good work!

[Alex_Michel]

Obvious troll or spam bot. Leaning towards spam bot. That reply is 100% AI generated.

[Velopura]

 438 mile per hour KOM. How does this get past auto flagging? Ridiculous.

[anchskier]

@mal @Jane @Scout - What is so hard about creating some basic controls on activities that would filter out OBVIOUSLY bad activities?  How can someone load a "ride" that has an average of 45mph with an average heart rate of 67bpm over 56 miles and your system does not question it?  This is F-ing ridiculous!  See the activity below for just one example.  This happens ALL THE TIME, yet somehow your programmers can't figure out how to screen these out?  

Afternoon Ride | Ride | Strava (https://www.strava.com/activities/12044135676)

[Rdhb]

Strava made this announcement over a year ago, and I'm still getting multiple notifications per day from people that have taken my KOMs and are very obviously driving cars. When is this actually going to be implemented?

[vmorande]

Well, If you don't process past activities righ after having a decent algorithm, we are doomed because they are piling and with 10 flags a day it's impossible to keep local segments clean.

[DannyDindia]

Look at these awesome activities that were not flagged automatically:

https://www.strava.com/activities/11162527264#3216134935065909580
https://www.strava.com/activities/11214927165/overview

400 km/h average speed!

[Alex_Michel]

Impossible!

(Sarcasm)
We’re updating our algorithms to make leaderboards more credible, and taking steps to proactively prevent suspicious efforts from appearing on leaderboards – so you can trust that the results you see are accurate.

(/sarcasm)

---

@DannyDindia wrote:

Look at these awesome activities that were not flagged automatically:

https://www.strava.com/activities/11162527264#3216134935065909580
https://www.strava.com/activities/11214927165/overview

400 km/h average speed!

---

- Strava

[bandit_74]

I often find that when using some Garmin devices (I test many of them) with the energy-saving mode activated, the GPS detects fewer points.
I have noticed that some KOMs appear on my profile but unfortunately (!) they are incorrect.
It's easy to identify them because they have a higher average speed than the maximum speed, which is actually impossible.
This occurs on very short segments.
I suggest implementing a simple yet effective check: a segment where the average speed is higher than the maximum is mathematically incorrect and impossible, it should be not reported in the KOM lists.
What do you think about this?