Is 1767225600 the start of 2026?
Yes. 1767225600 is the Unix timestamp in seconds for January 1, 2026 at exactly 00:00:00 UTC.
The Unix timestamp 1767225600 is January 1, 2026 at 00:00:00 UTC. It marks the exact start of calendar year 2026 in UTC, so it is a useful boundary value for API tests, database filters, log searches, and scheduled jobs.
Keep the unit clear before converting. 1767225600 is a 10-digit epoch-seconds value. The equivalent 13-digit milliseconds value is 1767225600000.
17672256002026-01-01 00:00:00 UTC2026-01-01T00:00:00.000Z1767225600000Start of 2026 in UTCPaste 1767225600 into the Unix timestamp to date converter. The UTC result should read January 1, 2026 at midnight. If your local display shows December 31, 2025, that is a timezone display effect, not a different epoch value.
To create the timestamp from a readable date instead, open the main epoch time converter and enter 2026-01-01 00:00:00 with the timezone set to UTC. You can also use the broader epoch to date guide for unit rules and date-format examples.
timestamp >= 1767225600 for events at or after the start of 2026 UTC.1767225600000 when a JavaScript Date constructor expects milliseconds.Yes. 1767225600 is the Unix timestamp in seconds for January 1, 2026 at exactly 00:00:00 UTC.
The millisecond timestamp is 1767225600000. Multiply Unix seconds by 1000 when a JavaScript or browser API expects milliseconds.
No. The raw epoch value is a UTC instant. Timezone only changes the displayed local calendar date and clock time.
That can happen when the result is displayed in a timezone west of UTC. The UTC value is still January 1, 2026 at 00:00:00.
Related Tools
More free tools for developers debugging timestamps, schedules, and text changes.