A lot of cycle computers will disregard stopped time and give you an average on running time only, fairly sure mine does that. But I use a Garmin 200 now, and that works the same way, but a cycle computer is more accurate if set up correctly.

As long as you are completely stationary a cycle computer isn't recording averages though Phill, averages only being recorded against motion. Of course walking a bike makes an average very low.

 

N.B. Crossed with Arstu's post above.

I had a Garmin 200, but chasing the stats (and anyone else in front of me), often left me so breathless I felt sick, so I sold it on ebay and bought the 500 with the HR strap (good sense isnt my strongest attribute) I dont exactly understand HR zones, but I know when it goes into the 170's its time to slow down!! Now I just use it and upload to Strava which nicely displays weekly totals n stuff. With the e bike I make the hilly rides private to avoid any confrontation. Last week I got 3 KOM's coming up Ilkley moor so dare not publish that!!

@[mention=2339]Artstu[/mention], interesting re bike computers being more accurate, my readout on the Bs10 is always optimistic in both distance and mph/av mph compared to strava and endomondo which are both within a nb of each other, although iam sure i read something on the net that the kalkhoff/Bosch were renowned for being 8% optimistic.

I like optimistic!!

Yes the GPS varies quite a lot, understandable given the huge distance it operates over. I get quite varying distances and elevation figures for identical rides. My friend gets some wild GPS traces from here phone all the time.

I read somewhere that phones in general were more accurate because they use cell towers as well as the built ion GPS.. Especially under trees and among high buildings...

Most accurate speeds/distance/averages of all are from wired cycle computers, especially if accurately set and then fine tuned against a known mileage route.

 

I have an exact 4.9 mile measurement course which I ride at a constant distance from the road edges through bends. Then any error in recorded distance on that test run I tune out by fine adjustment of the wheel diameter setting in the cycle computer.

 

If I change the tyre type that's on the measurement wheel, I reset the fine tune by repeating that test run.

I use a Satmap 10 with their whole UK map card ( a recent and dramatic drop in price allowed me to upgrade from the Central England map card) It gives me all the data I require (average moving speed, time cycling , total time total ascents and allows routes to be pre-set). Probably does loads more but I have not needed to delve deeper.

I have never checked it's absolute accuracy however actual distance to pre-set route is always pretty close.

I'm mostly riding unassisted atm swapping between my MTB and single speed racer, MTB average in the 12-13mphs and other 15-19mph both in strava. Strava has racked up 963 miles since the new year, not too shabby.

I'm mostly riding unassisted atm swapping between my MTB and single speed racer, MTB average in the 12-13mphs and other 15-19mph both in strava. Strava has racked up 963 miles since the new year, not too shabby.

 

Not bad, someone I follow has done 2,800 miles so far this year, with 215,000 feet of climbing !