Dinner is one of the more dependable fixed points in a household, and everything before it — the oven, the table, calling everyone through — works backwards from that time. If 6:55 pm is when it lands, this page counts down to it precisely, updating every second without anything to press.
Coming back to this page in an hour, tomorrow or next month shows exactly the same thing: however long is genuinely left until 6:55 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.
Matching what somebody said against what somebody wrote is easier with all three versions to hand: 6:55 pm for everyday reading, 18:55 for anything printed in railway style, and five to seven in the evening 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
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.
What is 18:55 in the 12-hour clock?
That is 6:55 pm, or five to seven in the evening if you are saying it aloud. From 13:00 onwards, subtracting twelve gives the pm figure — the same moment written three different ways.
Does the number update by itself?
Yes. It recalculates every second from your device's clock, so there is nothing to refresh or restart. Whatever is on screen is the current gap to the target time, not a figure worked out when the page first loaded.
What happens if 6:55 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.
Cookie policy