Overnight travel puts departures at hours nobody would choose, and a coach or a check-in at 11:13 pm is not moved by how inconvenient it is. This page counts down to that time exactly, so the last hour before leaving can be spent packing rather than doing arithmetic.
Coming back to this page in an hour, tomorrow or next month shows exactly the same thing: however long is genuinely left until 11:13 pm 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.
Twelve o'clock is where the 12-hour clock is at its weakest, since 12 am and 12 pm are read the wrong way round often enough to cause real trouble. Writing a time as 23:13 removes the problem outright, because a 24-hour figure only ever points at one moment in the day.
Common questions
What happens if 11:13 pm 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 11:13 pm, 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