Why fifteen minutes is the unit calendars agree on
Fifteen minutes is the smallest slot that calendar software, billing systems, timetables and transport schedules all agree to draw. Four to the hour, thirty-two to a standard eight-hour day, and — the property that makes it special — it maps onto the clock face without remainder. A quarter-hour timer started on a quarter mark finishes on a quarter mark, which means you can plan around it without doing any arithmetic at all.
That is a real, practical difference from its neighbours. Ten minutes from 09:25 ends at 09:35, a time that means nothing to anybody. Fifteen minutes from 09:15 ends at 09:30, which is a slot boundary somebody else has probably already booked. The finish-time table below is built from quarter-mark starts on purpose, so you can check the property for yourself.
The uses follow the grid. Stand-ups are fifteen minutes because a quarter hour is the smallest unit a calendar will defend. Homework gets chunked into quarter hours because a child can see the end of one on a clock face. Ovens get checked on the quarter. Parking, practice, phone calls and waiting rooms all quietly run on the same grid.
A quarter hour is where sloppy timers start showing
Fifteen minutes is roughly the point at which the drift of a naive countdown crosses from invisible into merely small. Projected from the rate we measured, a tick-counting timer finishes a quarter hour about 5.3 s late on an idle page, and 10 s late on a page doing other work. Nobody will spot that on a single run.
The reason to care is the grid again. The value of a quarter-hour timer is that it lands on the mark; a timer that finishes 10 s late has stopped doing the one thing that made the quarter hour worth using. Repeat it across the thirty-two quarter hours of a working day and the projected accumulation on a busy page is 327 s of slot boundaries that are no longer boundaries.
This page holds the mark because it never counts ticks: it fixes the end instant when you press start and re-derives the remaining time from the monotonic clock on every frame. The measurement that produced these rates — including the runs that were timed directly, with nothing projected — is on the main timer page.
Making the quarter hour hold
Start on the mark. The whole benefit is alignment, and it only exists if you begin at :00, :15, :30 or :45. Starting at :07 gives you fifteen accurate minutes that end at a meaningless time.
Decide what the alarm means before you start it. A quarter hour is long enough that people forget what they agreed the end signal was for. "Stop" and "check on it" need different reactions, and the timer cannot tell them apart.
Do not stack quarter hours by hand. Four in a row is an hour of clicking reset at exactly the moment you are least willing to look at a screen. Either use the 1 hour timer and check the clock at the quarters, or use the Pomodoro cycle, which alternates work and rest without being touched. For the shorter half of the grid, the 5 minute timer and 10 minute timer behave identically.
The numbers behind a 15 minutes timer
Every row here is worked out from the duration itself: the conversions are arithmetic on 900 seconds, and the accuracy rows come from the drift measurement described on the home page. The source column says which is which.
One disclosure belongs beside the table itself, where you will actually read it: those drift figures were measured in Node v22.20.0 on one Windows desktop, not in a browser (win32 10.0.26200, AMD Ryzen 9 9950X3D 16-Core Processor, on 2026-08-14). Each condition was run 5 times and the figures used here are the medians, because single runs of this kind vary by more than the difference they are being used to describe. Your machine will produce different numbers. What transfers is the shape — a counter that accumulates drifts, and a counter that subtracts from a fixed instant does not.
| 15 minutes timer | Value | Source |
|---|---|---|
| Length in seconds | 900 s | arithmetic |
| Length in milliseconds | 900,000 ms | arithmetic |
| Share of one hour | 1/4 | arithmetic |
| Ticks a naive 1-per-second counter makes | 900 | arithmetic |
| Finish lateness of a naive counter, idle page | 5.3 s | projected |
| Finish lateness of a naive counter, busy page | 10 s | projected |
| Share of the timer lost to one 3-second frozen tab | 0.3% | derived |
| Quarter hours in one hour | 4 | arithmetic |
| Quarter hours in an eight-hour day | 32 | arithmetic |
| Projected drift across a full day of quarter hours, busy page | 327 s | projected |
Start now, finish when?
The most common question about any fixed-length timer is what time it lets you out. These finish times are computed at build time from the start time plus 900 seconds, so the rows that cross midnight are right for the same reason the rest are.
| If you start | Start (24 h) | Start (12 h) | It ends | Ends (12 h) | Day |
|---|---|---|---|---|---|
| Stand-up, on the hour | 09:00 | 9:00 AM | 09:15 | 9:15 AM | same day |
| Second quarter of the morning | 09:15 | 9:15 AM | 09:30 | 9:30 AM | same day |
| Last quarter before noon | 11:45 | 11:45 AM | 12:00 | 12:00 PM | same day |
| Half past, ending on the quarter | 17:30 | 5:30 PM | 17:45 | 5:45 PM | same day |
| Final quarter hour of the day | 23:45 | 11:45 PM | 00:00 | 12:00 AM | next day |