Tea time in a house with children is less a meal than a schedule, with everything before it timed to land in the right order. If 2:31 pm is when it needs to be on the table, the countdown here is more use than an estimate, updating continuously as the afternoon runs down.
Rather than rounding to the nearest minute, the count tracks hours, minutes and seconds the whole way down, in one line. That precision matters most in the last stretch, when the minutes turn into single figures and the difference between leaving now and leaving shortly stops being academic and starts costing you the train.
Matching what somebody said against what somebody wrote is easier with all three versions to hand: 2:31 pm for everyday reading, 14:31 for anything printed in railway style, and twenty-nine minutes to three in the afternoon for whatever was actually spoken down the phone. All three describe precisely the same point in the day, and having them side by side saves a good deal of squinting at a timetable.
Common questions
What happens if 2:31 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 2:31 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