HOME ARTICLES JOIN GALLERY STORE SPONSORS MARKETPLACE CONTACT US  
Register | FAQ | Search | Memberlist
Username:    Password:       Forgot your password?
BIKELAND > FORUMS > ZX-14.com > Thread: Speedo Error NEW TOPIC NEW POLL POST REPLY
S A Kruz


Expert Class
Posts: 127
posted July 07, 2006 12:03 PM        
Speedo Error

Anybody used a gps or radar gun to check speedo accuracy? At 80 mph indicated, how fast are we actually going?
____________
2007 CBR 1000RR Red/Black Yoshimura RS-5 Full System, Flapper Mod and PCIII
2006 ZX-14 Passion Red, Flies Out, Yoshimura TRC, PCIII, TRE006a and Custom Map
2004 VTX 1300C Candy Apple Red

  Ignore this member   
zerMATT


Pro
Posts: 1931
posted July 07, 2006 12:12 PM        Edited By: zerMATT on 7 Jul 2006 13:12
You might search some old threads, there has been LOTS of discussion about this. The consensus is generally 7-10% optimistic with tire wear being one important factor.
____________
'06 Passion Red ZX-14 | Black D&D Slip-ons | Speedo Healer | V1 | zumo 550 | Heli-Risers | PhantomX

  Ignore this member   
iflyphi


Zone Head
Posts: 542
posted July 07, 2006 03:08 PM        
71.982458797413987410449663363333333 Mph. Satellite tracked by Norad. Just kidding. Set it at 8% low and it will be dead on. Or set it at 20% low and increase your resale value. Lower means less miles, and it sure looks cool when you know your going like a 100, and it indicating 80, and your getting 44 mpg.
  Ignore this member   
TJ


Zone Head
Posts: 604
posted July 07, 2006 04:11 PM        
quote:
Anybody used a gps or radar gun to check speedo accuracy? At 80 mph indicated, how fast are we actually going?


Mine was 7% off (as stated in many other threads)...

  Ignore this member   
All times are America/Va < Previous Thread     Next Thread >
BIKELAND > FORUMS > ZX-14.com > Thread: Speedo Error NEW TOPIC NEW POLL POST REPLY

FEATURED NEWS   Bikeland News RSS Feed

HEADLINES   Bikeland News RSS Feed


Copyright 2000-2026 Bikeland Media
Please refer to our terms of service for further information
0.22847199440002 seconds processing time