Why didn't my atomic watch change for daylight saving time?

The usual explanation, and the first one NIST gives, is that the watch missed the signal. That is half of it. The other half is what the signal actually says about daylight saving, which differs from station to station, and what the watch has been told to do with it. We read what the agencies publish about their time codes, set it against nine Citizen instruction manuals and Mexico's 2022 time law, and turned it into a rule for each signal and the setting each place needs.

What each time signal says about daylight saving

Which stations your watch can reach, and from how far, is set out in our answer on whether an atomic watch will work where you live. What they send about daylight saving differs:

The split matters. DCF77 and MSF send local time with summer time already in it, and PTB says the zone bits show "to which time system the time information transmitted after second mark 20 refers" in every minute, so a watch that misses the one-hour warning is put right by its next good reception. WWVB sends UTC, and the watch works out the local hour from the bits and your settings. That is why this is mostly an American problem. JJY's SU1 and SU2 are, in NICT's words, "reserved for future additions to the time code, such as information on daylight savings time. Currently, both bits are always transmitted as 0." Japan does not change its clocks; anyone relying on JJY elsewhere switches summer time by hand.

Fall back night in the US, hour by hour

NIST's own publication on its time services gives the rule: "On the day of a change from DST back to ST bit 57 changes from 1 to 0 at 0000 UTC, and bit 58 changes from 1 to 0 exactly 24 hours later." On 1 November 2026, 0000 UTC falls on Saturday evening across the US. A watch that hears the two bits disagree knows the change is coming at the next 2:00 a.m. local time. The table puts that into local time for each zone.

Watches do not listen in the evening. Citizen's H800 tries at 2:00 and 3:00 a.m., the H149 and U680 at 2, 3 and 4 a.m. That still works, because the bits disagree for the whole UTC day: a clock that misses the evening window, in the WWVB summary Tom Van Baak quoted on the time-nuts list in 2016, "should apply the DST change on the next update after that", and from Sunday evening both bits read standard time. So one good reception after the change is enough, provided the watch is set to act on it.

The setting that stops it: automatic or manual

NIST's help page, after reception: "some clocks have a way to disable Daylight Saving Time. Make sure it isn't disabled if your area observes DST." On Citizen watches the setting has two parts: which time to show now, and whether the signal may change it.

On the H800 chronograph, a hand points to 12 o'clock for automatic and 6 o'clock for manual: "While manual setting is enabled, the summer time ON/OFF setting is not changed even when the watch receives the time signal." Pull the crown out and hold the lower right button for two seconds to switch. Three manuals show how a watch lands on manual without the owner meaning it:

• H149: correcting it by hand switches automatic off. "If you show the standard time manually, the watch will not show Summer Time when receiving the time signal." Fix this weekend's hour that way and it will not spring forward in March 2027 either. Selecting summer time turns automatic back on; then receive the signal to return to standard time.
• E650: one manual change locks it. It "engages the manual override", and "the only way to cancel the manual override is to do the all reset and 0-Positioning".
• U680: automatic is the factory setting, and it is per home city. After a reset the receive setting returns to "AU", which updates the home city's summer time from the signal. The manual adds: "There may be cases when the time is not changed on the appropriate date."

For automatic summer time, the U680 manual adds, "the home city must be a city within the reception area". Our guide to world time watches covers home and local cities, and the world timer entry explains why only a watch with the rules in firmware can follow daylight saving at all.

Places that do not follow the US rule

A watch on automatic applies WWVB's bits to every city it assigns to the US station. Citizen's H800 and H149 even link Anchorage, Los Angeles, Denver, Chicago and New York, showing "Summer Time/standard time in common".

• Arizona. No daylight saving. NIST's advice: "make sure that DST is disabled on your radio controlled clock. Not all clocks have this feature, so you might have to select another time zone." The H800 has no Phoenix, so use Denver set to standard time; that city then "always shows the standard time" whatever the others do. Arizona and Denver agree from November to March, so a wrong setting only shows in spring.
• Hawaii. No daylight saving, and Honolulu is 5,380 km from Fort Collins; Citizen marks it out of range. Set standard time once and leave it.
• Mexico. The Ley de los Husos Horarios, in force from 30 October 2022, applies seasonal time "únicamente" in the northern border area and repealed the 2002 summer time decree. Mexico City has not changed its clocks since.
• Mexico's northern border. Article 5 keeps seasonal time for all of Baja California and listed municipalities in Chihuahua (Juárez, Ojinaga), Coahuila (Acuña, Piedras Negras), Nuevo León (Anáhuac) and Tamaulipas (Nuevo Laredo, Reynosa, Matamoros). It runs "desde las dos horas del segundo domingo de marzo" to "las dos horas del primer domingo de noviembre": the US dates and the US hour. A watch set to the neighbouring US city on automatic is right there.

Mexico City is where an automatic watch goes wrong by itself. Citizen's U680 lists Mexico City as a US-signal city at UTC−6, and on AU updates each city's summer time from its area's signal, so it takes US summer time from March to November: an hour fast all summer. At about 2,430 km from WWVB, inside Citizen's widest range, it can hear the signal. The cure is STD MA. A watch that has been an hour fast there since March and puts itself right on 1 November is doing exactly this.

Satellite watches were never told

Citizen's GPS satellite watches are often called atomic too. The F950 manual repeats it throughout: "Summer time (DST) information is not contained in the satellite signal. Adjust the setting manually before and after the summer time (DST) period." A satellite watch never changes for daylight saving by itself. The Citizen page covers which families use which system.

If the hour is right but the minutes are wrong

Daylight saving moves the time by exactly one hour; as NIST puts it, "minutes and seconds are the same in all time zones... only hours are different." A watch a few minutes or seconds out after a successful reception has a different fault.

It is the hands' reference position: the zero the watch counts its hand steps from, which Citizen compares to zeroing a weighing scale. The H486 manual: "The reference position may become misaligned by environmental factors such as magnetism, static electricity or an external impact. Even if radio signals are received, if the watch hands are not aligned to the correct reference position, it will not be possible to indicate the correct time." Citizen's global FAQ gives the same answer to "The time of my radio controlled watch is slightly wrong. Why?"

On the H486, hold button B for more than five seconds and the hands should stop at 00:00:00, which "could take up to a maximum of about 7 minutes"; if not, the manual's adjustment procedure resets them. Other calibers use other buttons. Our answer on whether magnets can damage a watch explains why a quartz watch's motor is the part they upset. A mechanical watch whose hands miss the markers is a different matter, covered in our page on misaligned hands.

What to do tonight

1. Decide what the error is. Exactly one hour out: daylight saving or zone. Anything else: reference position, above.
2. Check the home city. Your own zone, on the station you can receive.
3. Check the summer time mode. AU if you live where the clocks change on the US dates; STD MA in Arizona, Hawaii and most of Mexico.
4. Check the last reception. Many Citizen watches, the H800 among them, show OK or NO with the seconds hand.
5. Force a reception. By a window, still, 9 o'clock side toward the station on a Citizen, using on-demand reception or the 2:00 a.m. attempt. A solar watch in low charge will not receive; our answer on charging a solar watch gives the times, and the Eco-Drive entry explains the cell.
6. If it still will not receive, switch summer time by hand, and check whether that turns automatic off, as on the H149 and E650. On a watch without the setting, turning the hands back an hour is safe, as our answer on turning the hands backwards shows.

Without reception the watch is an ordinary quartz watch, about ±15 seconds a month on the H800, the usual figure in our answer on quartz accuracy; timing it at home over a week shows whether it is receiving. A mechanical GMT has no daylight saving logic at all; see setting a GMT watch.

When this answer stops applying

• Your manual says otherwise. The Citizen behaviour above is from the H800, H820, H874, H149, H610, E650, U680, F950 and H486 manuals read on 28 October 2026. We could not read Casio's or Seiko's manuals for this page, so Casio and Seiko owners should check their own.
• The rules change. Citizen warns that "summer time rules may change depending on the country or area". A watch on automatic follows the signal's rule, not your local law, as Mexico City owners found after 2022.
• The station is off the air. A watch that has not synced for several nights may be waiting for the transmitter, not misbehaving.