How to Measure Watch Accuracy at Home

Measuring a watch's accuracy requires no equipment. Compare the watch against a trusted reference time, note the difference, then compare again at least 24 hours later. The change in that difference, divided by the days elapsed, is your watch's daily rate in seconds per day. Every tool that exists for this — apps, timegraphers, timing machines — is just a faster or more precise way of doing that one comparison.

The principle: two comparisons, hours apart

A watch's rate is how much it gains or loses per day, written as seconds per day (s/day). A watch running +5 s/day gains five seconds every 24 hours; one at −3 s/day loses three. A single comparison against a reference clock tells you nothing about rate — it only tells you the watch was set imprecisely at some point. You need two comparisons separated by time, because rate is the change in offset, not the offset itself.

That's the whole method. Everything below is about doing those two comparisons carefully enough that the number you get reflects the watch and not your measurement technique. For context on what number you should be hoping for, see how accurate a mechanical watch should be — the short version is that a few seconds per day either way is normal for most mechanical movements.

Method 1: your watch vs. atomic time, by hand

This is the free, no-download method, and done carefully it resolves a watch's rate to better than a second per day.

First, pick a reference. The gold standard in the US is time.gov, the official NIST/USNO time display. A smartphone's own clock is also acceptable: phones sync to network time and typically sit within a fraction of a second of true time. What you must avoid is anything that free-runs — wall clocks, microwave ovens, car dashboards, older desktop computers. These can drift by seconds per week, and if your reference drifts, that drift gets silently added to your watch's measured rate.

Then take the first reading. At the exact moment the reference ticks over to a full minute, look at your watch's seconds hand and note the offset — "watch is 4 seconds ahead," for example. Reading at the top of a reference minute makes the comparison easier, because you only have to judge one moving hand instead of two. Write the offset down with the date and time. Then leave the watch alone: don't reset it, don't let it stop, and if it's a hand-wound watch, keep it wound as you normally would.

At least 24 hours later, repeat the reading against the same reference. Subtract the first offset from the second and divide by the days elapsed. If the watch was +4 seconds yesterday and is +10 seconds today, it is running at +6 s/day.

The two pitfalls

Reference drift is the first, covered above: use atomic or network time, and use the same reference for both readings so any constant offset cancels out.

Reading error is the second, and it's why the 24-hour minimum matters. Judging a seconds hand against a reference is good to maybe a quarter or half second per reading, and you take two readings. That uncertainty is fixed — but the rate you compute divides it by the elapsed time, so the longer you wait, the less it matters:

Time between readingsCombined reading error of ±0.5 s becomes…
6 hours±2 s/day of rate uncertainty
12 hours±1 s/day
24 hours±0.5 s/day
48 hours±0.25 s/day

So a quick before-work and after-work check can't distinguish a +1 s/day watch from a +4 s/day watch. A full day between readings can.

Method 2: an app that timestamps for you

The manual method's weak point is the human: eyeballing a seconds hand against a ticking reference, twice, and keeping notes. An app can replace the eyeball with a timestamp. ChronoLog ($5.99 on iOS, Android in beta) does this with a quick-tap mode — you tap the moment your seconds hand hits a marker, and the tap is timestamped against atomic time — and a photo mode that reads the watch from a picture. Because each measurement is logged, the app accumulates a rate history per watch over days and weeks, which is exactly the repeated-measurement picture that a single manual check can't give you.

The principle is unchanged: it's still two (or many) comparisons against a reference, hours apart. The app just shrinks the reading error and does the bookkeeping.

Method 3: listening to the movement

For mechanical watches there's a third approach that doesn't wait 24 hours: measure the beat directly. A mechanical movement ticks at a fixed design frequency — commonly 28,800 beats per hour — and a timegrapher measures how far the actual beat spacing deviates from that ideal, converting it to seconds per day in moments rather than days. Watchmakers use dedicated machines with contact sensors; a phone's microphone can do the same job through the air, with typical accuracy of ±2–5 s/day and no extra hardware. If you're curious how a phone mic pulls a tick out of background noise, the audio timegrapher deep dive walks through the signal processing.

The trade-off: an acoustic reading is a snapshot of the watch in one position, at one state of wind, on a table. It's superb for diagnosis — is this watch wildly out, does it have a beat error, does the rate swing between positions — but the number that matters for daily wear is the averaged rate on your wrist, which only the two-readings-over-time methods capture. The two approaches answer different questions, and they complement each other.

How long to measure for a trustworthy number

One 24-hour measurement gives you a real number, but a mechanical watch doesn't have a single fixed rate. It runs differently dial-up on a nightstand than crown-down in a drawer, differently fully wound than half wound, and slightly differently warm on a wrist than cool on a desk. Any single day's figure folds all of that into one number.

A practical schedule: take a reading at the same time each day for five to seven days while wearing the watch normally. The average over the week is your watch's real-world rate; the spread between the best and worst day tells you how position-sensitive the movement is. If the daily figures cluster within a couple of seconds of each other, you can trust the average. If they swing widely, that variation is itself information — see the next section.

Reading your results: fast, slow, and position

Consistently fast or slow by a few seconds a day is the normal case. A steady +4 s/day is a healthy watch; whether it's worth regulating depends on the movement's spec and your tolerance, not on the sign of the number.

Different rates in different positions is also normal, within reason. Gravity loads the balance pivots differently dial-up versus crown-down, so resting position changes the rate. You can use this: if your watch runs fast on the wrist, find an overnight resting position that runs slow, and the two partially cancel. Test it by measuring 24-hour rates with the watch left in one position overnight each night — dial up, dial down, crown down — and comparing.

A sudden change — a watch that was +3 s/day for months and is now +40 — is a symptom, not a personality shift. Magnetization is the most common culprit for sudden gains; a fading mainspring or thickening oils show up as a gradual drift. Why a watch runs fast or slow covers how to tell the cases apart and what's fixable at home.

Track your watch's rate automatically

ChronoLog timestamps your measurements against atomic time, builds a rate history for every watch in your collection, and includes an audio timegrapher — $5.99 one-time on the App Store.