Share.

15 Comments

  1. Were you going downhill?

    I’ve definitely hit speeds that high or higher when going downhill.

  2. HypobromousAcid on

    Man I wish I could take advantage of gravity. Last time I descended a mountain the gradient was -15% to -25% and descending was absolutely terrifying combined with winding mountain roads.

  3. Sometimes there are glitches that happen with odd spikes. Sometimes it’s legit. 60kph downhill isn’t that nuts, but if it wasn’t downhill it could be a data outlier

    The other day I went skiing and hit 60mph. There’s no possible way this happened. Maybe a quick movement of my body or something when it was sampling.

  4. the app graph has less resolution than the website. it’s not likely bad data. that’s not terribly fast or unreasonable speed.

  5. I remember being 14 and cycling with my dad down some steep hills here in Ohio. I think our top speed around that age was probably 70 ish km/h and omg it was freaking terrifying.

  6. Seems reasonable. My top speed (sensor on my rear wheel, not gps) was 84km/h, going downhill can make you go fast.

  7. Do you have a wheel speed sensor? If not, it’s likely to be a glitch. GPS estimates speed by measuring how far you travel between position fixes, and if it has a couple of poor quality fixes it can give some weird numbers for speed. I’ve had mine tell me I jumped across a canyon and hit over 180 km/hr on a mountain bike ride before. A speed sensor gives you the actual speed the wheel is going.

    On a road bike, you’d have to pedal rather fast to keep up in the highest gear at 61 km/hr. Just something else you can compare your measured speed to and see if it seems reasonable.

Leave A Reply