Time Conversion: Hours, Minutes, Seconds, Days & Weeks

Key Takeaways

Core chain: 1 min = 60 s; 1 h = 60 min = 3,600 s; 1 day = 86,400 s; 1 week = 604,800 s

Decimal hours: 0.25 h = 15 min; 0.1 h = 6 min — timesheets live on this

Year math: 365 days = 8,760 h = 525,600 min; work year ≈ 2,080 h (40h × 52w)

Fun scale: 1 million seconds ≈ 11.6 days; 1 billion seconds ≈ 31.7 years

Core answer: 1 day = 24 h = 1,440 min = 86,400 s; 1 week = 168 h; 1 year ≈ 365.25 days ≈ 8,766 h ≈ 31.56 million seconds. Payroll math uses 21.75 average working days/month (China standard); a year has 52 full weeks plus 1–2 extra days, which is why weekday calendars drift.

The conversion spine

Unit	Equals
1 minute	60 s
1 hour	60 min = 3,600 s
1 day	24 h = 86,400 s
1 week	7 days = 168 h
1 month (avg)	30.44 days = 730.5 h
1 year	365.25 days ≈ 8,766 h
1 decade / century	10 / 100 years

The year's fine print

Why 365.25: Earth orbits in 365 d 5 h 48 m 46 s; leap years add Feb 29 every 4 years, skip centuries (1700, 1800, 1900), unless divisible by 400 (2000 was a leap year).
52 weeks + 1: 365 = 52×7 + 1, so next year's same date lands one weekday later (two after leap years).
Months are uneven: 31, 28/29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 — knuckle mnemonic still works.

Worked examples

Example 1 — Hourly wage conversion. ¥10,000/month salary: 21.75 days × 8 h = 174 h → ¥57.5/h. Overtime at 1.5× = ¥86/h weekday, 2× = ¥115 rest day, 3× = ¥172.5 holiday.

Example 2 — Project estimate. "3 person-weeks" = 3 × 40 = 120 person-hours; at 6 effective hours/day that's 4 calendar weeks, not 3 — plan with efficiency factors.

Example 3 — Streaming data usage. 2 h/day of 1080p video (~3 GB/h) for a month: 60 h = 180 GB — time-to-data conversions run household budgets.

Example 4 — Machine uptime. 99.9% yearly uptime allows 8.77 h of downtime; 99.99% allows 52.6 min; each "nine" costs real engineering money.

Common mistakes and myths

100-minute hours — 1.5 h = 1 h 30 min, not 1 h 50 min; timesheets in decimal hours trip everyone.
A year = exactly 52 weeks — it's 52.18 weeks; payroll systems using "weekly × 52" underpay vs monthly by a hair.
Forgetting time zones in durations — a 14:00–16:00 "2-hour" call spanning a DST change may be 1 or 3 real hours.
Leap second blindness — UTC occasionally gains a second (27 so far); high-precision systems must not assume 86,400 s/day always.
Treating months as 4 weeks — 4 weeks = 28 days ≠ a month; "biweekly vs semimonthly" payroll differ by 2 checks a year.

Frequently Asked Questions

How do time units convert?

The 60-60-24 chain: 1 min = 60 s; 1 h = 60 min = 3,600 s; 1 day = 24 h = 1,440 min = 86,400 s; 1 week = 168 h = 10,080 min; 1 month ≈ 30.44 days average; 1 year = 365.25 days average = 8,766 h. Unlike metric, nothing is base-10 — the 12/24/60 structure is 4,000 years of Babylonian inheritance.

How do decimal hours work on timesheets?

Minutes ÷ 60 = decimal hours: 45 min = 0.75 h; 20 min = 0.333 h. Reverse: 0.1 h = 6 min; 0.25 h = 15 min; 0.5 h = 30 min. So 7.6 h = 7 h 36 min (0.6 × 60), NOT 7 h 60 min. Payroll rounding rules often snap to 0.1 or 0.25 h — a 7-minute task billed at 0.25 h is legal but accumulates; know your system's rounding.

How do I add and subtract clock times?

Convert to minutes, operate, convert back. 2 h 50 min + 1 h 35 min: 170 + 95 = 265 min = 4 h 25 min. Borrow carefully across the 60-boundary: 3 h 10 min − 1 h 45 min → 2 h 70 min − 1 h 45 min = 1 h 25 min. Crossing midnight: 22:30 + 5 h = 27:30 − 24 = 03:30 next day. 24-hour format eliminates AM/PM ambiguity entirely.

How many work hours are in a year?

40 h/week × 52 = 2,080 h baseline. Subtract ~10 public holidays (80 h) and 10-15 leave days: realistic 1,840-1,920 h. Part-time and freelance capacity planning starts from these numbers, not 2,080. Day-rate sanity check: annual salary ÷ 1,900 ≈ effective hourly rate — ¥380k/year ≈ ¥200/h, which reframes both overtime and outsourcing decisions.

How big are a million and a billion seconds?

1 million seconds = 11 days 13 h 47 min — a vacation. 1 billion seconds = 31.7 YEARS — a career. The 2,700× jump from million to billion is the cleanest intuition for how misleading "billion" sounds. A 32-bit signed integer counting seconds from 1970 (Unix time) overflows in 2038 — the Y2K38 bug lives in this arithmetic.

What mistakes happen with time conversion?

(1) 1.5 h read as 1 h 50 min (it is 1 h 30 min — decimals of hour are sixtieths); (2) 0.1 h = 10 min (it is 6); (3) adding across midnight without the ±24 h wrap; (4) time-zone math forgetting date-line crossings (a 14-h flight departing Monday noon can arrive Monday morning); (5) month = 4 weeks (it is 4.35 — 12 × 4 = 48 weeks, not 52, which is why "4-week months" shortchange annual totals by 4%).

Common scenarios

Quick reference