How Long Until Thursday? Hours, Minutes and Days Left

The count above runs to 00:00 on the next Thursday in your own time zone, ticking once a second.

Thursday is the last day of the week that still behaves like a working day at both ends. Anything that has to be finished before the week runs out tends to be aimed here rather than at Friday, which is why so much scheduling clusters on it: releases, board meetings, invoices, the deadline set so that Friday is left for the fallout.

If you are counting to a Thursday deadline, read the working days figure and not the day count. From a Friday afternoon the two are six days and four working days, and it is the four that decides whether the plan holds.

To count to a Thursday weeks away, or to a specific time on it rather than midnight, put that into the box or use the countdown.

How to use it

Read the count at the top: days, hours, minutes and seconds, moving as you watch.
Look below it for the same span as whole days, weeks and working days.
Change the date in the box to count down to anything else instead.

Questions

Can I count to Thursday at a set time rather than midnight?

Yes. The box takes a time as well as a date, so a nine o'clock meeting or a five o'clock cutoff counts down to the moment it actually happens. The page starts at midnight only because that is when the day itself begins.

How many working days is it to Thursday?

It depends where you start, and the working days figure below the clock does the counting: Monday to Friday, from tomorrow up to and including the Thursday. Public holidays are not subtracted, since they vary by country and by year and the page has no way to know which apply to you.

Does it handle a clock change during the count?

Yes. The count is worked out from your device's own calendar rather than by adding a fixed number of hours, so a week that contains a daylight saving change is 167 or 169 hours and the count says so instead of drifting an hour out.

How many hours is that, rather than days?

The count above is already in hours, minutes and seconds as well as days, and the figures below it give the whole span in each unit on its own. A day boundary is not a day of distance: at eight in the evening, tomorrow is four hours away rather than one day away, and it is the hours that decide whether something is worth starting tonight.

Which time zone is this counting in?

Yours, the one your device is set to. The target is midnight in your own local time rather than midnight UTC, because a question about a weekday is a question about the calendar on your wall. Someone reading this in another country sees their own answer, not a translation of anybody else's.

Does it keep counting while I leave the tab open?

Yes, it ticks once a second for as long as the page is open, and picks the count back up from the clock when you return to the tab. Nothing is stored between visits, so opening it again simply asks your clock what time it is now.

Is any of this sent anywhere?

No. The arithmetic runs in WebAssembly inside this tab, and the only thing it reads is your device clock. There is no account, no cookie of ours and no record of what you looked up. Load the page once and it keeps working with the network off.

The same question, other days

Each of these counts to the start of its own day, in your time zone, with the same live seconds and the same working days figure.

Your data stays on your device

Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. You can load this page once, go offline, and it still works.

This page makes no requests at all, to anywhere. That is not a promise in the copy: it is a Content-Security-Policy header your browser enforces, and connect-src on it is none. Open the network tab and watch nothing happen.