I've posted about this loads before in the Garmin thread but the problem isn't time with the 800, it's distance. I have had my 800 freeze up and brick 157 miles into a 200 mile ride with a moving time of 13.5 hours and a total time of less than 19.
This is a known problem among audaxers - do a search on YACF for more info. The answer is to reset and start a new track every 200-250km then stitch them back together later because the problem is the size of the track file not the elapsed time.
Aside from this 'feature' I've found my 800 extremely reliable and it's still going strong after five and a half years.
If you want to know if a Garmin is any good ask an audaxer because they actually ride their bikes properly ;)
The 810 is widely acknowledged to be less good than the 800, as @hippy says.
I've posted about this loads before in the Garmin thread but the problem isn't time with the 800, it's distance. I have had my 800 freeze up and brick 157 miles into a 200 mile ride with a moving time of 13.5 hours and a total time of less than 19.
This is a known problem among audaxers - do a search on YACF for more info. The answer is to reset and start a new track every 200-250km then stitch them back together later because the problem is the size of the track file not the elapsed time.
Aside from this 'feature' I've found my 800 extremely reliable and it's still going strong after five and a half years.
If you want to know if a Garmin is any good ask an audaxer because they actually ride their bikes properly ;)
The 810 is widely acknowledged to be less good than the 800, as @hippy says.