How Many Seconds in a Day, Week and Year?
There are 86,400 seconds in a day (24 × 60 × 60), 604,800 in a week, 31,536,000 in a 365-day year and 31,622,400 in a 366-day leap year. Those are the everyday answers, and the table below gives every common period. The more interesting answers are the exceptions: a day with a clock change has 82,800 or 90,000 seconds on the local clock, an “average” calendar year is 31,556,952 seconds, and from 1972 to 2016 a few UTC days had 86,401 seconds because of leap seconds. This guide gives the numbers, the arithmetic behind them, and which one to use when. Facts are as of November 2026.
Key facts (as of November 2026)
- Day: 86,400 s. Week: 604,800 s. Hour: 3,600 s.
- Year: 31,536,000 s (365 days) or 31,622,400 s (366 days); 2027 has 365 days and 2028 has 366.
- Average Gregorian year: 31,556,952 s (97 leap years every 400 years); Julian year: 31,557,600 s.
- The second itself is defined by caesium: the frequency ΔνCs is fixed at “9 192 631 770 when expressed in the unit Hz” (BIPM).
- Clock-change days in 2027 have 82,800 s (spring) or 90,000 s (autumn) where clocks change (our calculation, tzdata 2026f).
- 27 leap seconds were added to UTC between 1972 and 2016; none since (tz leapseconds file).
Seconds in each period
All values were computed twice: by multiplication in a script, and by subtracting Python datetime values (for example January 1, 2028 minus January 1, 2027). Calendar periods use the Gregorian calendar.
| Period | Seconds |
|---|---|
| Minute | 60 |
| Hour | 3,600 |
| Day | 86,400 |
| Week | 604,800 |
| 30-day month | 2,592,000 |
| 31-day month | 2,678,400 |
| February (28 days) | 2,419,200 |
| February in a leap year (29 days) | 2,505,600 |
| Common year (365 days) | 31,536,000 |
| Leap year (366 days) | 31,622,400 |
| Average Gregorian year (365.2425 days) | 31,556,952 |
| Julian year (365.25 days, used in astronomy) | 31,557,600 |
| Decade 2020–2029 (three leap years) | 315,619,200 |
| Century 2001–2100 | 3,155,673,600 |
The century figure is 36,524 days because 2100 is not a leap year under the Gregorian rule (years divisible by 100 are leap years only if also divisible by 400). For converting minutes and hours into decimals for timesheets, see our time card calculator; for a full calendar, see 2027 calendar.
Which “year” should you use?
- A specific calendar year: 31,536,000 s for a common year such as 2027, 31,622,400 s for a leap year such as 2028.
- Long-run averages (interest, population rates, “per year” statistics): the Gregorian average of 365.2425 days, or 31,556,952 s.
- Astronomy and light-years: the Julian year of exactly 365.25 days, 31,557,600 s.
- Quick estimates: about 31.5 million, or “π × 10⁷”, which is 31,415,927, within 0.4% of a common year.
A billion seconds is therefore about 31.7 common years (1,000,000,000 ÷ 31,536,000 = 31.71), or 31.69 average Gregorian years.
Days that are not 86,400 seconds long
A local calendar day is longer or shorter when the clocks change. We measured each 2027 change day as the real time between two local midnights, using Python zoneinfo on IANA tzdata 2026f, and re-read the offsets with the C library’s localtime().
| Day (2027) | Where | Clock change | Length in seconds |
|---|---|---|---|
| Sun, Mar 14 | New York and most of the US and Canada that still change | Forward 1 hour | 82,800 (23 hours) |
| Sun, Mar 28 | London, Paris, the EU | Forward 1 hour | 82,800 |
| Sun, Apr 4 | Lord Howe Island, Australia | Back 30 minutes | 88,200 (24.5 hours) |
| Sun, Oct 31 | London, Paris, the EU | Back 1 hour | 90,000 (25 hours) |
| Sun, Nov 7 | New York and US zones that change | Back 1 hour | 90,000 |
| Any day | Phoenix, Tokyo, Vancouver (since Nov 2026), UTC | None | 86,400 |
Lord Howe Island is the odd one: it is the only zone in tzdata 2026f that shifts by 30 minutes in 2027 (we scanned every zone), so its April change day has 88,200 seconds. Places that no longer change clocks, like British Columbia since November 1, 2026 and Manitoba, now always have 86,400-second days; one consequence is that British Columbia’s local year 2026 is one hour short, 31,532,400 seconds, because it sprang forward in March and never fell back. In New York, by contrast, 2027 has exactly 31,536,000 seconds: the hour lost in March is returned in November. See clock changes 2026–2027 for every country’s dates.
Software that assumes every day is 86,400 seconds of local time gets these days wrong: adding 86,400 seconds to midnight on March 14, 2027 in New York lands at 1:00 AM on March 15, not midnight. Add calendar days in local time, or do the arithmetic in UTC, as explained in our epoch time guide.
Leap seconds: the 86,401-second days
UTC itself has also had long days. Between 1972 and 2016, 27 leap seconds were inserted, each making one UTC day 86,401 seconds long (the minute had a 61st second, 23:59:60). The tzdata package’s leapseconds file lists all 27. None has been added since December 31, 2016, and our leap seconds guide explains the decision to stop them. So, counting leap seconds, 2016 had 31,622,401 UTC seconds. Unix time ignores leap seconds and treats every day as 86,400 seconds, which is why it is simple to compute with; see Unix time and 2038.
What one second is
The second is defined by atoms, not by the day. The current wording from the International Bureau of Weights and Measures (BIPM) defines it “by taking the fixed numerical value of the caesium frequency ΔνCs” “to be 9 192 631 770 when expressed in the unit Hz, which is equal to s–1” (BIPM, the second). In plain terms, one second is 9,192,631,770 cycles of the radiation from a particular transition of the caesium-133 atom. Our guide how atomic clocks work covers how labs realise it.
The day, meanwhile, is set by Earth’s rotation, which is not perfectly steady. The “86,400” in a day is a convention that fits the atomic second to the average solar day closely enough that leap seconds were needed only 27 times in 45 years. For the difference between the solar day and the 23 h 56 min rotation day, see sidereal day vs solar day; for why the day has 24 hours at all, why 24 hours in a day.
Quick conversions
- Seconds to minutes: divide by 60. 1,000 s = 16 min 40 s.
- Seconds to hours: divide by 3,600. 10,000 s = 2 h 46 min 40 s.
- Seconds to days: divide by 86,400. 1,000,000 s = 11 days 13 h 46 min 40 s.
- Hours to seconds: multiply by 3,600. A 40-hour week is 144,000 s.
How we checked
Each period was computed by multiplication and again by subtracting Python datetime objects; leap-year counts use Python’s calendar module (97 leap years in 2001–2400). Change-day lengths are the UTC difference between consecutive local midnights in tzdata 2026f zones (America/New_York, Europe/London, Australia/Lord_Howe, America/Vancouver), re-checked with glibc localtime(). Leap seconds counted from the leapseconds file in the tzdata 2026f package. The BIPM definition was read on November 9, 2026.
Sources
- BIPM, SI base unit: second
- IANA time zone database (version 2026f, includes the leapseconds file)
- IANA tz “australasia” source file (Lord Howe Island rules)
- Python documentation, calendar.isleap
Frequently asked questions
How many seconds are in a day?
86,400 (24 hours × 60 minutes × 60 seconds). Days with a clock change have 82,800 or 90,000 seconds of local time.
How many seconds are in a year?
31,536,000 in a 365-day year such as 2027 and 31,622,400 in a 366-day leap year such as 2028. The average Gregorian year is 31,556,952 seconds.
How many seconds are in an hour?
3,600.
How many seconds are in a week?
604,800.
How many seconds are in a month?
2,419,200 (28 days), 2,505,600 (29), 2,592,000 (30) or 2,678,400 (31). The average Gregorian month is 2,629,746 seconds.
How many years is a billion seconds?
About 31.7 years.