Anyone rostered on through the small hours — a hospital ward, a mine site, an emergency call centre — tends to watch the clock differently at this time of night. If the shift, the round, or the handover lines up with 12:22 am, this page gives the exact run-down to it, updating every second rather than leaving you to do the maths on a tired brain.
The numbers shown here run on your own device's clock, checking the time continuously and recalculating the gap to 12:22 am every second. There is nothing to press and nothing to configure — the countdown is already running the moment the page finishes loading, and it keeps updating for as long as you are looking at it.
Cross-checking a time against a roster written in an unfamiliar format is easier with more than one version on hand — 12:22 am for the everyday reading, 00:22 for anything printed the other way, and twenty-two minutes past twelve at night for matching against whatever someone actually said out loud. All three point to exactly the same moment.
Common questions
Can I use this to time something happening tomorrow instead of today?
The countdown always points to the next time that moment occurs, so if it has already passed for today, it is already counting down to tomorrow's occurrence without any adjustment needed.
Does daylight saving affect the countdown?
Yes, because it reads from your device's own clock, any daylight saving change your device applies automatically is reflected in the countdown without any extra step on your part.
Why does the countdown look different on two devices checked at once?
That usually means the two clocks are not perfectly in sync, or one device has not adjusted for a time zone or daylight saving change. The countdown itself always follows whatever clock it is reading from.
Is there a way to make the countdown count towards a different time?
This particular page is fixed to one target time. Checking a different one just means visiting the matching page built for that specific time instead.
Cookie policy