Why Your GPS Watch Is Wrong on the Track

There's a LetsRun thread with the complaint in one line: "Strava can't even figure out that a running track is 400m." Every athlete who has worn a GPS watch to a track session knows the feeling — the rep was 150m, the watch says 0.11 miles, and next Tuesday the same rep will say something else. On r/trackandfield, an athlete asking for a better way put it plainly: not a tracker, "because those are very inconsistent when running a 150m."

This isn't a defect in your particular watch. It's structural, and it's worth understanding before you spend another season arguing with it.

The error doesn't shrink with the rep

Consumer GPS positions drift by metres — how many depends on sky view, buildings, and luck that day. Over a 10k on open roads, that noise averages out into a distance you can live with. That's the use case the watch was built for, and there it's genuinely good.

A track rep inverts the math. The error stays the same size while the rep gets shorter, so the error's share of the measurement grows. A few metres of drift is a rounding error across ten kilometres and a headline across 150. Same watch, same accuracy, opposite outcome — the instrument didn't change, the denominator did.

Curves are the worst case

A GPS watch samples your position at intervals and connects the dots with straight lines. On a straight road, chords and reality agree. On the tight radius of a track bend, chords cut the corner every single sample — the watch runs tangents you never ran. A rep with a full bend in it systematically reads short, and reads differently short depending on where in the bend each sample happened to land.

Add the stagger and it gets worse: the watch has no idea you were in lane five, where the bend is longer and the geometry is different. And many tracks sit inside stadiums, next to grandstands and metal fencing — exactly the multipath environment where GPS positioning is at its flakiest.

Pace is derived, so it's doubly wrong

Everything on the watch face downstream of distance inherits the problem. Pace is distance over time with the distance wrong. "Instantaneous" pace is also smoothed, so it lags hard efforts that are shorter than the smoothing window — which is most track reps. A 150 @ 95% can be over before the watch has finished deciding you sped up.

The distance being wrong also poisons the season view. If Tuesday's 150s logged as 140-something and next week's log as 160-something, every downstream number — weekly fast-running volume, average rep pace, the trend line you actually care about — is built on sand. Consistent wrong would at least be comparable. GPS on a track isn't even that.

The workarounds, honestly rated

• Manual lap mode. Turn off auto-lap, hit the lap button at start and finish, ignore the distance field entirely. This works — because it turns your GPS watch into a stopwatch you happen to be wearing.
• Track mode. Some watches detect the oval and snap laps to 400m. Helps for continuous lap running; helps much less for a broken session of 150s starting mid-bend from a stagger, which is where the problem lived in the first place.
• Buying a more expensive watch. The geometry above does not read spec sheets. Better antennas trim the noise; they don't change what a chord is.

What to do instead

Stand on the one piece of measurement infrastructure you already have: the track. It's certified. The 150 is 150.0m today and 150.0m in March. The only variable worth instrumenting is time.

So: known distance, hand time, written down. A coach or teammate with a stopwatch — or your own thumb — plus a log entry like 6×150 @ 95%, 4' rest: 18.42, 18.31, 18.55, 18.20, 18.47, 18.12. Label hand times as hand times and be consistent, and your March-vs-October comparison is clean in a way no satellite estimate of a curve will ever be. (For the full logging system — jumps and throws included — see how to log track workouts.)

The community's standing answer to the tracker problem has been "enter it manually" for years. They're right. Trackbuddy is built on exactly that premise: you time it, the log remembers everything. No GPS required — on the track, GPS was never really invited.