In midwinter there is no light at all at this hour — London barely manages a sunrise before eight, and Scotland waits considerably longer. That makes the clock the only honest guide to how far the night has run. This page counts down to 1:58 am against your device's own time, second by second.
Coming back to this page in an hour, tomorrow or next month shows exactly the same thing: however long is genuinely left until 1:58 am next comes round. There is no session to lose and nothing to configure again, because the number is worked out fresh each time from the clock on your device.
Said out loud, 1:58 am usually comes out as two minutes to two at night rather than as a string of digits. Spoken and written time diverge more than people expect, which is worth remembering when somebody tells you a time over the phone and you are trying to match it against something printed.
Common questions
What happens if 1:58 am has already gone for today?
The count simply carries on towards the next occurrence, which is tomorrow. That rollover happens on its own — the page does not need reloading and there is nothing to reset by hand.
Which clock does it use?
Your own. It reads the local time and time zone from the device you are looking at, so the figure reflects where you actually are rather than a fixed zone written into the page.
Will this alert me when the time arrives?
No. It is a live number rather than an alarm — nothing rings, buzzes or notifies you at zero. If you need to be interrupted at 1:58 am, set an alarm as well and treat this page as the running total.
Is it affected by the clocks changing?
Only in the sense that your device is. When the change between GMT and BST happens at the end of March and October, the device adjusts and the countdown follows it without anything to do here.
Cookie policy