NUMBERS IN THE NEWS / Everyday life & time
Fall back: when 8 clock hours last 9
Where the U.S. fall-back was observed on November 1, midnight to 8 a.m. read as eight clock hours but lasted nine. Check any interval with UTC offsets.
THE TAKEAWAY
Subtracting clock labels is not enough across an offset change. Convert both endpoints to the same time basis before measuring the duration.
One hour appears twice
The October 29 USPS notice puts the fall-back on November 1. NIST explains the transition: in observing locations, the clock returns from 2 a.m. daylight time to 1 a.m. standard time. The hour labeled 1 a.m. happens twice.
That makes this local midnight-to-midnight civil day 25 elapsed hours long. It does not make the hour itself longer or promise an extra hour of sleep. The result depends on whether the location observes this clock change.
A NUMBERBENCH ORIGINAL · TRY IT
Repeated-hour elapsed-time calculator
Example: November 1 in New York, midnight EDT to 8 a.m. EST. Change the offsets to model another pair of endpoints.
Offsets are entered explicitly; the tool does not infer a location, date or time-zone rule. For the repeated 1 a.m. hour, specify the offset of each occurrence. A negative clock subtraction can still be valid across that repeated hour. Inputs stay in your browser. This is time arithmetic, not a pay, overtime, legal or sleep recommendation.
No clock change in your interval? Use the time duration calculator. Converting between zones? Try the time zone calculator.
Follow the offsets, not just the hands
For the New York example, midnight at UTC−4 corresponds to 04:00 UTC. Eight a.m. at UTC−5 corresponds to 13:00 UTC. Subtract the two UTC times and nine hours have elapsed. Subtract only the local clock labels and the answer appears to be eight.
The calculator uses that same endpoint conversion. Its adjustment is the start offset minus the end offset, expressed in hours. It accepts breaks separately so the underlying duration stays visible; the result does not determine how an employer should record or pay for time.
Which 1:30 do you mean?
A repeated local time needs an offset or another explicit way to distinguish its two occurrences. For example, 01:45 at UTC−4 to 01:15 at UTC−5 is 30 minutes forward in elapsed time, even though the clock labels appear to go backward.
Use the offsets that actually apply to your endpoints. The form does not infer them from your location or choose between repeated times for you. If the end is on a later calendar date, enter the number of calendar days crossed. For an ordinary interval with no offset change, use the same offset at both ends.
Make it your number
This calculator is embedded above. The default example is on one calendar date, so days crossed is zero. Change the time labels, endpoint offsets and breaks to model your own interval. It calculates elapsed time only; it does not interpret payroll, overtime or legal requirements.
Try the repeated-hour calculatorSources & context
Data period: November 1, 2026 U.S. fall-back where observed; October 29 USPS notice. Source checked November 1, 2026. This article preserves the release vintage; later estimates may differ.
- USPS — Daylight saving time ends on Sunday
Released October 29, 2026. Dated official notice identifies November 1 at 2 a.m. and a one-hour backward change in areas where it is observed.
- NIST — Daylight Saving Time Rules
Released February 9, 2026. Page update date is February 9, 2026. It specifies the 2 a.m. to 1 a.m. repeated hour and identifies regions that do not observe DST.
- US Naval Observatory — 2026 daylight-saving dates
Source accessed November 1, 2026. Official calendar lists the 2026 ending date as November 1; calendar access is not labeled as a release date.
Examples and graphics are NumberBench calculations or illustrations, labeled above. How we calculate · Report a correction