How Long Until Tuesday? Days, Hours and Minutes Left

The count above runs to 00:00 on the next Tuesday in your own time zone, and keeps ticking for as long as you leave the page open.

Tuesday is where the phrase "next Tuesday" causes the most trouble, because it sits far enough into the week that both readings are plausible. Say it on a Monday and half the room hears tomorrow while the other half hears eight days from now. This page always means the next Tuesday to arrive, which is the reading that never needs a follow-up question.

It is also the weekday most often carrying something that repeats: the standing meeting, the bin collection, the weekly release. For those, the number worth reading is the plain hours, since a thing that happens at nine in the morning is nearer than the day count makes it sound.

For a specific Tuesday rather than the next one, type its date into the box, or use the countdown for any date at all.

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

Does this count to tomorrow if today is Monday?

Yes. The target is always the next Tuesday to arrive, so asked on a Monday it counts the hours left in Monday rather than jumping a week ahead. Asked on a Tuesday it counts up from midnight instead, telling you how far into the day you already are.

Why does it say hours rather than one day?

Because a day boundary is not a day of distance. At eight in the evening on Monday, Tuesday is four hours away, and rounding that up to "one day" is the error that makes people miss things. The count shows hours and minutes for exactly that reason.

Can I count to a Tuesday several weeks out?

Yes, put the date in the box and the count moves to it. The date then travels in the link, after the # , so you can send the same countdown to somebody else and they see it running against their own clock.

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.