Run pace disparity between Fitbit, Strava and Enmondo

[ShaunyB]

Hi all

Does have anyone have any ideas about this? I used my Fitbit Blaze, linked with Strava to measure my training runs. Because I like the training plans on Endomondo, I export the GPX file for the run from Strava and import it into Endomondo.

Fitbit measures the pace as 7:57 per km, Strava 7:56 and Endomondo 7:53... all with same run and files originated from my Fitbit. I've done nothing to alter it at all. It's annoying because I'm trying to train for a marathon and sometimes the pace difference can be as much as 12 seconds and it's obviously screws up my training pace.

I know this probably isn't directly Fitbit related but anyone?

Regards,

   Shaun

[Mukluk4]

With Strava and fitbit being a second apart, that could be as simple as how it's rounded, no big deal.

Since Strava is your source of data for Endomondo, sounds like you need to speak to the Endo people on how it interprets whatever data it's using.

[ShaunyB]

I agree. I've sent their support an email including the GPS file. It
happens all the time and ss I'm following a marathon training plan, very
annoying.

I'll let you know what they say.