BB200: Moving time VS elapsed time
Moderators: Bearbonesnorm, Taylor, Chew
BB200: Moving time VS elapsed time
Another thread has an interesting tangent; the comparison between people’s moving and elapsed time.
For those with a Garmin (most of us it would seem) please post your moving and elapsed time
Might be interesting to some.
For those with a Garmin (most of us it would seem) please post your moving and elapsed time
Might be interesting to some.
Re: BB200: Moving time VS elapsed time
Total time: 19h25
Moving time: 18h36
Elapsed time: 28h00
Source: Garmin Fenix 5 Sapphire via Garmin Connect
Comments /Issues:
Not sure the difference between “total time”, and “moving time”
Seven punctures!!!!
Only three spare inner tubes
Primary Garmin (Montana 610) played silly buggers, used backup (Garmin Edge 1000)
Moving time: 18h36
Elapsed time: 28h00
Source: Garmin Fenix 5 Sapphire via Garmin Connect
Comments /Issues:
Not sure the difference between “total time”, and “moving time”
Seven punctures!!!!
Only three spare inner tubes
Primary Garmin (Montana 610) played silly buggers, used backup (Garmin Edge 1000)
Re: BB200: Moving time VS elapsed time
19:13:13
Moving Time
27:45:17
Elapsed Time
4.9 mph
Avg Speed
6.5 mph
Avg Moving Speed
I had garmin charging issues so had to stop at Llangurig to charge it.
Moving Time
27:45:17
Elapsed Time
4.9 mph
Avg Speed
6.5 mph
Avg Moving Speed
I had garmin charging issues so had to stop at Llangurig to charge it.
-
- Posts: 2380
- Joined: Thu Dec 15, 2016 7:52 pm
- Location: Peoples Republic of Devon
Re: BB200: Moving time VS elapsed time
Total time: 22h 51min
Moving time: 20h 22min
Source: Etrex 30x via Strava
Moving time: 20h 22min
Source: Etrex 30x via Strava
If you are going through hell, keep going.
WSC
WSC
Re: BB200: Moving time VS elapsed time
Elapsed time: 17:02
Moving time: 15:04 (according to Strava)
Source: Garmin Edge 800
I don’t use auto-pause, so the moving time calculation would be down to Strava to figure out, as I uploaded directly from the GPX track. For ITT efforts, I am primarily focused on average speed over elapsed time and auto pause just confuses that for me.
Moving time: 15:04 (according to Strava)
Source: Garmin Edge 800
I don’t use auto-pause, so the moving time calculation would be down to Strava to figure out, as I uploaded directly from the GPX track. For ITT efforts, I am primarily focused on average speed over elapsed time and auto pause just confuses that for me.
- whitestone
- Posts: 7866
- Joined: Thu Dec 04, 2014 10:20 am
- Location: Skipton(ish)
- Contact:
Re: BB200: Moving time VS elapsed time
Garmin Oregon showed 20hrs moving time and 1hr20 stopped time. Strava has moving time as 19hrs10 and stopped time as 2hrs10. So 50mins difference.
Without doing a test to see how the Oregon and Strava handle momentary pauses such as gates then it's pretty much guesswork as to the algorithm used.
10% stopped time isn't too bad though especially in those conditions when common sense is telling you to seem shelter.
Without doing a test to see how the Oregon and Strava handle momentary pauses such as gates then it's pretty much guesswork as to the algorithm used.
10% stopped time isn't too bad though especially in those conditions when common sense is telling you to seem shelter.
Better weight than wisdom, a traveller cannot carry
Re: BB200: Moving time VS elapsed time
BB300
Total: 34hrs 11mins
Moving: 26hrs 38mins (Strava)
Source: Edge 1000
Auto pause off. Massive differential caused by endless stops to deal with tyre leaking air / then tubes puncturing / then stuffing tyre with grass.
Total: 34hrs 11mins
Moving: 26hrs 38mins (Strava)
Source: Edge 1000
Auto pause off. Massive differential caused by endless stops to deal with tyre leaking air / then tubes puncturing / then stuffing tyre with grass.
Re: BB200: Moving time VS elapsed time
Ah so you used my grass suggestion. Glad to hear it works in skinny tyres as well as fat tyres.Richard G wrote:BB300
Total: 34hrs 11mins
Moving: 26hrs 38mins (Strava)
Source: Edge 1000
Auto pause off. Massive differential caused by endless stops to deal with tyre leaking air / then tubes puncturing / then stuffing tyre with grass.
Re: BB200: Moving time VS elapsed time
"Works" might be a bit strong. But I think it reduced the chance of rim damage.
Re: BB200: Moving time VS elapsed time
It wasn't working too well when we caught up.......
34:18 total time, and 24:17 riding time on strava..
10 hours either sleeping, eating, or dealing with gates!
34:18 total time, and 24:17 riding time on strava..
10 hours either sleeping, eating, or dealing with gates!
- In Reverse
- Posts: 1821
- Joined: Mon Oct 12, 2015 9:08 pm
- Location: Manchester
Re: BB200: Moving time VS elapsed time
22:25 elapsed, 18:01 moving, 11.0km/h ave speed (Strava)
4hrs 20min stopped time sounds about right for a couple of power naps, pint at The Bluebell, butty and drinks at the petrol station and all the gates. I usually faff a lot on rides and expected I would have wated a lot more time than that.
4hrs 20min stopped time sounds about right for a couple of power naps, pint at The Bluebell, butty and drinks at the petrol station and all the gates. I usually faff a lot on rides and expected I would have wated a lot more time than that.