Love WatchTracker
Very good
Love it!
Thank you!!
Very accurate
I just wish the UI would be a bit nicer and more intuitive
Works great
Was a great app until the data corrupted
Still the Best After All These Years
This app is not a timegrapher that gives instant readings on your watch’s rate. Instead, it collects data points by having you match your watch’s time to the app’s time (or atomic time). Using at least two reference points, the app then calculates, graphs, and tracks your watch’s rate. You can start a new time run anytime you adjust your watch, and you can also track multiple watches with the app.
The only real requirement for accuracy is having quick reflexes—because you need to tap the screen when your watch shows the exact time displayed on the app. If you can’t tap within about 0.2 to 0.5 seconds of the shown time, the results might not be as accurate or meaningful.
Whether you’re a casual collector or a serious watch enthusiast, this app is a must-have if you care about tracking your watch’s accuracy over time. It’s easy to use and gives you detailed insights into how fast or slow your watch is running—something any watch lover will appreciate.
5 stars
Brillant! 👌🏻
Doesn't work
Great Tool to track all watches
It can even track high precision Quartz watches in the seconds per year range, albeit you have to send the author a short note and ask for individual activation. This feature really should be integrated in the standard festure set.
Strongly recommended app!
Great app (but broken on iPhone 16 pro - FIXED)
Update: worked out that if I close the app on iPhone, log a new data point on a timing run on iPad and then open the iPhone app afterwards, it’ll work again. Maybe corrupted data that the forcing of an iCloud sync (with the adding of the new data point) is fixing/repairing?
Update2: The recent update (Nov/Dec 2025) seems to have done the trick. No issues since.
Perfect
Not working with iOS 26
The perfect app?
Great app but broken on iPhone 16 pro
Update: worked out that if I close the app on iPhone, log a new data point on a timing run on iPad and then open the iPhone app afterwards, it’ll work again. Maybe corrupted data that the forcing of an iCloud sync (with the adding of the new data point) is fixing/repairing?
