@Cunobelin @Eribiste has mentioned that the auto pause is on, besides it depends on the site, as you say there is moving avg, and overall avg, most sites will use a moving avg, if you upload a ride to strava that has no auto-pause or a file where its been stripped out (happens with some gpx exports) then strava i know will show the overall time as the moving time.
There is also a a lag between stopping and starting and the auto-pause feature to kick in, also with the 200 only working from a gps fix it can sometimes think you are moving whilst stationary (as sometimes two gps plots can be recorded as being further apart than they are), this can lead to an increment in time especially as it takes time to react and could increase the apparent moving time, however this is more usually seen as in abnormal max speeds. Even using a gps with a sp sensor (which is much more accurate) losses some speed on strava.
On my last ride I did 34.53 miles in 2:04:35.86 @ 16.6 according to the data from the 705 on GTC, the same ride the data from the R20 35.54 miles in 2:04:28 so basically 8's longer (this is ride time) @16.65mph, the 705 has the auto feature set and the R20 must take it into account, the same data from strava is 34.5 miles in 2:06:05 or 16.4mph (using the edge 705 data) so strava reckons on an extra 1min 35's or so,
so it reads the data in the same tcx file differently to that of GTC, I won't even start on the elevation thing.
For the record my overall avg sp for the same ride was 15.21mph.
