How Long Until Saturday? Days, Hours and Minutes Left

The count above runs to 00:00 on the next Saturday in your own time zone, which is midnight at the end of Friday.

Saturday is the one weekday whose position in the week nobody argues about and whose position on the calendar everybody does. Under ISO 8601, the week starts on Monday and Saturday is day 6, the first day of the weekend. On an American wall calendar the week starts on Sunday, so Saturday is the last column and the weekend sits split across the two ends of the grid. The day is the same; only the picture moves.

Because Saturday is not a working day, the working days figure beside the clock stops at Friday. Counting from a Monday it reads five, and it will read five from Tuesday counting to the Saturday after next as well, which is the arithmetic that catches people out when a weekend sits in the middle of a plan.

For the weekend rather than the day, see the weekend countdown. For any other date, the countdown takes one.

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

Is Saturday the sixth day of the week or the seventh?

The sixth under ISO 8601, the standard most software follows, where the week runs Monday to Sunday. It is the seventh on calendars that start the week on Sunday, which is the usual layout in the United States, Canada and Japan. Both describe the same day, and the count above is unaffected either way.

Does the working days figure count Saturday?

No. It counts Monday to Friday only, from tomorrow up to and including the target, so a count that ends on a Saturday includes every weekday before it and stops at the Friday. If you work weekends, the plain day count is the figure to read instead.

Can I count to a Saturday months away?

Yes. Type the date into the box and the count moves to it, with the same live seconds. The date lives in the link itself so you can share it, and it never expires, because there is nothing stored on a server to expire.

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.