Rank | User | Pace | Time | Date | Dist | Match |
---|---|---|---|---|---|---|
1 | The Duckinator | 8:11 | 2:01:47 | Nov 2015 | 14.89 | 90% |
2 | Anonymous | 10:40 | 2:39:23 | Oct 2016 | 14.94 | 89% |
3 | Anonymous | 11:15 | 2:49:18 Race |
Oct 2016 | 15.04 | 87% |
4 | Anonymous | 11:58 | 3:04:27 Trail Run |
Oct 2015 | 15.41 | 88% |
5 | Anonymous | 12:54 | 3:16:36 | Oct 2017 | 15.24 | 93% |
6 | mrs shanksi | 13:13 | 3:20:25 | Nov 2015 | 15.17 | 100% |
7 | Anonymous | 13:16 | 3:20:12 | Nov 2015 | 15.09 | 96% |
8 | Metro_Nome | 13:34 | 3:24:44 | Nov 2015 | 15.10 | 89% |
9 | Anonymous | 15:03 | 3:49:01 Fell Running |
Oct 2016 | 15.22 | 89% |
10 | IanS | 16:11 | 4:06:25 Race |
Oct 2016 | 15.22 | 86% |
11 | Anonymous | 16:47 | 4:18:10 Race |
Oct 2016 | 15.38 | 94% |
Year | Attempts | Best | Time |
---|
FAQ
Why are the distances all different?GPS watches are never 100% accurate. The data they record varies each time you run. And on top of that, you probably never take exactly the same racing line each time.
Some of the distances are way off
Our algorithm needs to simplify your route in order to help match it to others. Occasionally this means that if you take a slight detour on your route, it's still classed as a match.