This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FR935 upload to Strava shows Avg Pace & Strava iPhone App uses Avg Moving Pace

Former Member
Former Member
The same run recorded on both my FR935 and Strava iPhone App, and both uploaded to Strava show very different "Average Pace" values of 5:52/km (FR935) 5:10/km (Strava App). If I look at the Garmin Connect app it has a Avg Moving Pace of 5:14/km which is closer to the Strava App pace taking into account GPS differences. I would hope that Garmin upload my "Moving Time" to Strava rather that my "Total Time", that would be more equitable when comparing my run to other Strava users. Especially on runs with lots of traffic lights.

Regards

TJ
  • Strava pulls the data from Garmin; Garmin sends nothing, which is why you set the connection in Strava. Strava then does it's own thing with the data it gets from Garmin.
    The Strava app running on an iPhone will collect data differently from your 935. Strava will process that data differently to what Garmin does.
    They are not the same.
  • I turned auto pause of many years ago when using GPS devices. The device would stop if the signal became weak even if I was still moving - I do a lot of stuff in the bush or with overhead tree cover. I don’t pause the device at traffic lights or junctions so that’s never a problem. I’d recommend turning auto pause off on both rather than on on both.
  • Yes, but if you never pause your Garmin activity, then after uploading your activity, strava will automatically figure out when you were standing still and use that as your moving time anyway. It only uses the Garmin activity time as moving time when you pause your activity at least once. The real discrepency here is that strava uses moving time as the basis for average pace, and Garmin Connect uses activity time for average pace while having a secondary field for moving pace. And average pace is the big, representative number that shows up in the activity summary in both platforms, which causes confusion when they’re different.

    I suspect strava made this decision on moving time because auto pause is off by default for Garmin devices, so they decided to behave as if it was on, unless you pause it yourself.

    If you want the numbers to be the same, you have to either:
    - turn on auto pause for both
    - turn off auto pause for both and pause your Garmin activity at least once

    It’s just my preference, but I always pause my watch at stop lights for long runs, because I train by average pace and I don’t want time standing still to count. For interval workouts and races I don’t pause my watch, since for intervals, any time standing still is part of the workout (and you’re more interested in lap time than average pace).
  • Former Member
    0 Former Member over 7 years ago
    Thanks for the info on the differences in how Strava calculates moving time if you've paused in the activity vs if you don't hit pause. Thats really helped me get back to a consistent method of calculating moving time.

    I agree that auto-pause on trails doesn't really work that well if GPS gets a bit spotty.

    I also found that if I imported the Garmin file in a TCX format Strava calculates its own moving time.

    Cheers

    TJ