1767225600 is the start of 2026 in UTC
The Unix timestamp 1767225600 equals 2026-01-01T00:00:00.000Z. In plain language, that is January 1, 2026 at 00:00:00 UTC. It is the first second of 2026 when the year boundary is defined in UTC.
Seconds and milliseconds forms
The value 1767225600 is in Unix seconds. Some tools and programming languages expect milliseconds instead, especially JavaScript Date. Multiply by 1000 for the millisecond form.
- Unix seconds: 1767225600
- Unix milliseconds: 1767225600000
- ISO 8601 UTC: 2026-01-01T00:00:00.000Z
- JavaScript: new Date(1767225600 * 1000).toISOString()
- Linux: date -u -d @1767225600
Local timezone notes
UTC year boundaries do not always match local calendar year boundaries. The timestamp 1767225600 is still December 31, 2025 in some timezones west of UTC, including the United States. It is already January 1, 2026 in UTC and timezones east of UTC.
- UTC: 2026-01-01 00:00:00
- America/New_York: 2025-12-31 19:00:00
- America/Los_Angeles: 2025-12-31 16:00:00
- Europe/London: 2026-01-01 00:00:00
- Asia/Shanghai: 2026-01-01 08:00:00
How to compute any year-start timestamp
The start of any year in UTC is the Unix timestamp of January 1 at 00:00:00. Because years are not all the same length — leap years add a day — it is safest to let a date library compute the boundary rather than adding a fixed number of seconds to a previous year.
- JavaScript: Date.UTC(2026, 0, 1) / 1000 = 1767225600
- Python: int(datetime(2026, 1, 1, tzinfo=timezone.utc).timestamp())
- Linux: date -u -d '2026-01-01' +%s
- Start of 2025 in UTC: 1735689600
- Start of 2027 in UTC: 1798761600
End of 2026 and DST-affected local equivalents
The start of 2026 in UTC is 1767225600. The end of 2026 — the moment 2027 begins — is 1798761600. In between, every local wall-clock observation of "January 1, 2026 00:00" corresponds to a different Unix timestamp depending on the timezone.
- Start of 2026 UTC: 1767225600 = 2026-01-01 00:00:00 UTC
- End of 2026 / start of 2027 UTC: 1798761600 = 2027-01-01 00:00:00 UTC
- 2026 is a non-leap year: exactly 365 × 86,400 = 31,536,000 seconds
- Start of 2026 in New York (EST, UTC−5): 1767243600 — 5 hours later than UTC
- Start of 2026 in Los Angeles (PST, UTC−8): 1767254400 — 8 hours later
- Start of 2026 in Tokyo (JST, UTC+9): 1767193200 — 9 hours earlier
- Start of 2026 in London (GMT, UTC+0): 1767225600 — identical to UTC
- See the monthly breakdown for 2026 on the year reference page
FAQ
- What is the Unix timestamp for start of 2026?
- The UTC start of 2026 is Unix timestamp 1767225600 seconds, or 1767225600000 milliseconds.
- Is 1767225600 local midnight everywhere?
- No. It is midnight in UTC. In New York and Los Angeles it is still December 31, 2025.
- How do I verify 1767225600?
- Use an epoch converter, JavaScript new Date(1767225600 * 1000).toISOString(), or Linux date -u -d @1767225600.
- What is the Unix timestamp for the end of 2026?
- The last second of 2026 in UTC is 1798761599 (2026-12-31 23:59:59 UTC). For range queries, prefer the half-open boundary 1798761600, which is the exact start of 2027.