How this instrument works
A week is one of the few time units resting on no natural cycle whatsoever — no orbit, no rotation, nothing astronomical enforces a seven-day rhythm. It is simply seven days, and a day is fixed at 24 hours, so a week comes to exactly 168 hours: 7 × 24, with no rounding anywhere in that count. ISO 8601 formalises the same block, running Monday to Sunday for numbered calendar weeks, and BIPM's accepted-units table pins the day at 86,400 seconds beneath it all.
The seven-day week itself is older than any single calendar system that later adopted it — Babylonian astronomers tracking seven visible wandering lights and the Sabbath cycle of Jewish law both fed into it, and Rome made the cycle official empire-wide under Constantine in AD 321. What is comparatively recent is treating 168 hours as a meaningful total to budget against, rather than just a count of calendar days — a framing popularised well outside horology by writer Laura Vanderkam's 2010 book on time management, built around the observation that 24 × 7 always equals 168, whatever fills those hours.
Labour law leans on the same total from the opposite direction. The US Fair Labor Standards Act defines a workweek as 'a fixed and regularly recurring period of 168 hours — seven consecutive 24-hour periods' before measuring overtime against it, and the EU's Working Time Directive separately caps average working time, including overtime, at 48 of those 168 hours per week. Both rules quietly assume the same fixed total this page converts against.
- Type your total into the Hours (h) field — 168 is preloaded, exactly one full week.
- Read Weeks (wk) beneath it, recalculated on every keystroke to eleven decimal places.
- Fractional entries work fine: 84 hours, half a week, returns 0.5 wk exactly.
- Reversing direction, multiply any Weeks (wk) figure by 168 to recover an hour count.
- Negative entries are refused, since a duration cannot run to less than zero.
Worked example — a 168-hour on-call rotation
A remote research station schedules its duty engineer on a full weekly rotation, on call around the clock from Monday morning until the next Monday morning. Their roster logs that shift as 168 hours; enter 168 into Hours (h) and Weeks (wk) reads 1.0 — one complete week of coverage, no more and no less.
The same arithmetic exposes how little of that total a standard job actually occupies: a 40-hour working week, the US Fair Labor Standards Act's overtime threshold, is only 40 ÷ 168 = 0.238095… of this duty engineer's full on-call block. Whoever staffs the other 128 hours is covering more than three-fifths of the week the roster never bills as a normal shift.
Questions
Is a week always exactly 168 hours?
As a defined unit, yes — seven days of 24 hours each, with no rounding. Real clock weeks can differ slightly: a week containing a daylight-saving transition runs 167 or 169 clock hours depending on the direction of the shift, and, before their scheduled retirement by 2035, an inserted leap second could stretch a week by one extra second. This converter, like payroll and roster software generally, treats a week as the fixed 168-hour unit.
Where does the number 168 come from?
Simple multiplication: 7 days times 24 hours each. Unlike months or tropical years, a week is not chasing any astronomical cycle, so there is no approximation involved anywhere in this factor — 168 is exact, and dividing by it never introduces the kind of long repeating decimal that shows up converting hours to years or days to months.
How does a standard working week compare to a full 168-hour week?
It is a small fraction of it. The US Fair Labor Standards Act sets 40 hours as the threshold beyond which nonexempt employees earn overtime, which is 40 ÷ 168 ≈ 0.238 of a full week; the EU's Working Time Directive separately caps average working time, overtime included, at 48 of those 168 hours, or roughly 0.286. Both limits describe less than a third of the hours a week actually contains — the rest is sleep, rest days and everything outside paid work.
How do I convert weeks back into hours?
Multiply by 168. Two weeks becomes 336 hours; a 26-week contract becomes 4,368 hours. Because the factor is an exact whole number, this direction introduces no rounding at all — any decimal in your answer comes only from a fractional number of weeks you supplied, never from the conversion itself.
Does daylight saving time ever change a week's true hour count?
Only for the specific week containing the clock change, and only in wall-clock terms. Springing forward drops one hour, leaving that week 167 clock hours long; falling back adds one, making it 169. Elapsed-time arithmetic, and this converter, ignore that entirely and always treat a week as a flat 168 hours — the distinction matters mainly for payroll systems reconciling logged shift times against a calendar that briefly skipped or repeated an hour.
Why do full weekly on-call rotations get scheduled in hours rather than as 'one week'?
Precision at the boundary. A rota that logs 'one week' can be read as starting or ending at slightly different moments depending on which day is treated as the week's edge, while '168 hours from 08:00 Monday' names an exact handover instant down to the minute. Emergency services, remote research stations and hospital on-call schedules that run continuous weekly coverage typically specify the hour count directly for exactly this reason.