Running watch GPS accuracy explained: single-band vs dual-frequency

How a running watch works out where you are

A running watch fixes your position by listening to satellites. There are several global systems, GPS (American), GLONASS (Russian), Galileo (European), BeiDou (Chinese) and QZSS (Japanese), and a modern watch can use four or five of them at once. Each satellite broadcasts a precise time signal; by measuring how long signals from several satellites take to arrive, the watch triangulates your location, then repeats that roughly once a second to draw your route and calculate distance and pace.

In an open field with a clear view of the sky, almost any watch does this well, often within a couple of metres. The trouble starts when buildings, trees, hills or even your own body block or reflect those signals. A reflected signal arrives slightly late, the watch misreads the distance, and your logged position jumps. Multiply that error across thousands of position fixes in a run and you get the wandering trace and inflated distance that frustrate runners.

Single-band versus dual-frequency: the key difference

The biggest factor in real-world accuracy is whether a watch is single-band or dual-frequency (also called multi-band). A single-band watch listens to each satellite on one radio frequency, usually the L1 band. A dual-frequency watch listens on two, typically L1 and L5, for the same satellite at the same time. Because reflections affect the two frequencies differently, the watch can compare them, spot a corrupted signal and reject it. The result is a far cleaner position fix in exactly the places single-band watches struggle: city streets, tree-lined paths and steep valleys.

Of the watches we tested, the Coros Pace 3, Garmin Forerunner 265, Apple Watch Series 9 and Suunto Race are dual-frequency, while the Amazfit Bip 5 and Polar Pacer Pro are single-band. The gap between the two groups was the clearest pattern in our whole comparison.

What our testing showed

We ran every watch around the same loop, measured at exactly 10.00 km with a surveyor's wheel, with roughly 1.5 km under heavy tree canopy and 1 km between four-storey buildings, then repeated key runs to confirm the figures. The results split neatly along the chipset line:

• Coros Pace 3 (dual-frequency): 10.04 km, a 0.4% error, the most accurate watch on test.
• Apple Watch Series 9 (dual-frequency): 10.09 km, a 0.9% error.
• Garmin Forerunner 265 (multi-band): 10.12 km, a 1.2% error, with the fastest 8-second cold-start lock.
• Suunto Race (dual-band): a clean trace on every switchback, in the same accurate tier.
• Polar Pacer Pro (single-band): around 2.1% drift in the built-up section.
• Amazfit Bip 5 (single-band): up to 10.35 km, a 3.5% error, with a visibly zig-zagging trace under trees.

On a flat 400 m running track, the dual-frequency watches returned lap distances within 1 to 4 m of 400 m, while the Amazfit spread from 393 m to 409 m. The lesson is consistent: dual-frequency reception is what separates a watch you can trust for splits from one that is fine only for rough distance.

Why your watch says you ran further than you did

Almost every runner has finished a measured 10 km only for the watch to claim 10.2 or 10.3 km. The cause is nearly always GPS drift. When signals bounce off buildings or tree cover, the watch logs a slightly wandering path rather than the straight line you actually ran, and a wandering line is always longer than a straight one. Add up that wander across thousands of position fixes and the total distance creeps up. This is why single-band watches almost always over-read rather than under-read, and why the error is worse in cities and forests than on open roads.

It is rarely the course that is wrong. Officially measured race courses are accurate to within a fraction of a percent, so when your watch and the course markers disagree, the watch is the more likely culprit, especially on a twisting urban route. Running the tangents (the shortest legal line through bends) also adds apparent distance if your watch cuts corners differently from how you actually ran.

How to get the most accurate distance from any watch

You can squeeze better accuracy out of any watch with a few habits. Let it acquire a full GPS lock before you start, standing still for 30 to 60 seconds with a clear view of the sky rather than setting off the instant you step outside. Wear it on the wrist, snug but comfortable, so your arm does not block the antenna. Where your watch offers a multi-band or dual-frequency GPS mode, use it for races and accept the battery cost; save the lower-power modes for easy runs where exact distance matters less. And keep the watch's firmware up to date, as manufacturers regularly refine GPS algorithms.

Finally, set expectations by chipset. If you own a single-band watch, treat its distance as a close estimate and trust race markers over the watch on measured courses. If you want splits you can rely on to the second, that is exactly what a dual-frequency watch buys you, and it is the first thing to look for in our buying guide.