Bests & Worsts Reviews from Amazon

i have had this watch for about 3 months now. i have never owned any other type of gps enable watch before this one. however, my father owns the forerunner 305 and my mother has the forerunner 405 so i do still have some experience with those watches as well. in my opinion this is the best watch of the group hands down. the watch literally feels like a standard stopwatch. no extra weight, no extra bulk. the 405 does not quite fit like a normal watch due to the antenna extending down into the wrist strap. this watch is extremely comfortable to wear at all times and very adjustable in size (the holes go around the entire strap). this watch is very basic for runners and thus lacks the extra bells and whistles that the 305 and 405 have such as "ghost" trainers and "breadcrumb" directions. however this watch gives you current pace (more in just a moment), distance, calories, time, heart rate, and chimes at each "lap." for a standard running regimen this watch is more than enough to supplement a good, hard workout. CURRENT PACE EXPLANATION -i have noticed a lot of confusion about the idea of this watch lacking current "real-time" pace. However, to be quite honest, "real time" pace on a gps watch is pretty useless. the gps in the watch is NOT hooked up to a satellite CONTINUOUSLY. no gps in the world has this capability. instead, each gps has a certain "ping" time to send and receive a signal from a satellite. more advanced gps systems have quicker "pings" to more closely mimic a continuous connection but the connection is still never actually continuous. on watches that advertise "current pace," the watch is simply showing you the exact speed at which you were going between the last two pings. basically the watch calculates the distance traveled between each ping and then uses the time it took you to go that distance to get a speed. this leaves a lot of room for random spikes and troughs in the data. no human can run at a single speed across a certain distance. the human body simply cannot set itself to "cruise" and go from there. thus a "real time" pace is fairly useless for a runner. let me give an example. if someone were to turn on their forerunner 405 and set it to show current pace and run for 20 seconds at an 8:00min/mi pace, assuming the watch has a ping every 2 seconds or so, the data would look something like this: 6:52, 7:20, 8:15,7:47, 8:30, 6:59, 8:02, 8:10, etc...obviously this data is not really constant with an 8:00min/mi pace however the person may still very well be able to hit EXACTLY an 8:00min mile. What the forerunner 110 does, rather than show the data from EACH ping, is it takes each ping and adds it to a list with every other ping that has been recorded across the time frame and averages them all together. the final number that is shown on your watch will thus be called the "current AVERAGE pace." which in all honesty is MUCH more useful if one is trying to hit a certain pace goal. basically this current average pace can quite accurately depict your mile split well before you've reached the mile marker..if you speed up significantly then the ping data will thus be in a lower range and bring your "average" time down. now some of you might think that this means that the watch only displays a pace that doesnt refresh very often. however, the exact opposite is true. the watch will refresh the current average pace every time another ping comes in..so basically your current average pace could hypothetically move up or down with every single ping. but due to the beauty of the AVERAGE, the watch will not jump around sporadically like in a "current pace" but rather stay around a certain time and gradually move up or down according to your speed. in essence, the "current pace" on a lot of gps watches is really truly useless and most people will never end up using it because it doesnt actually give you any solid data to work off of. because the data is changing so dramatically each second, the data is just plain useless. FYI: some runners may have noticed very random spikes in their "fastest" pace that the garmin software will show after uploading the data. basically, "fastest pace" during your run means that for one single ping during the run you might have run a 5:34min/mile pace for all of 1 second. however, because that pace is still part of the data that is added into the overall time, it still counts as your "fastest pace" for the run even though your average mile pace for the workout was only 8:34... another nice thing about this watch is that after each run is saved to the history on the watch, it can be accessed to show the average pace over the entire distance rather than just the mile splits. the mile splits for older runs can only be accessed and viewed once the watch is connected to a computer and the data is uploaded. hope all of this has cleared up any confusion about current average pace for the forerunner 110!