1767225600 = Jan 1, 2026 00:00:00 UTC

The Unix timestamp 1767225600 converts to January 1, 2026 at 00:00:00 UTC. This is the exact first second of 2026 in Coordinated Universal Time, so it is commonly used as a boundary value in logs, SQL filters, API fixtures, and date conversion checks.

Treat 1767225600 as seconds. If your code expects milliseconds, use 1767225600000 instead.

Exact conversion

Epoch seconds
1767225600
UTC date
January 1, 2026
UTC time
00:00:00
Full UTC timestamp
2026-01-01 00:00:00 UTC
ISO 8601
2026-01-01T00:00:00.000Z
Epoch milliseconds
1767225600000
UTC weekday
Thursday

How to verify 1767225600

Paste 1767225600 into the Unix timestamp to date converter and read the UTC output. It should show 2026-01-01 00:00:00 UTC. For the reverse conversion, enter 2026-01-01 00:00:00 in UTC on the main epoch converter.

If a tool shows a different calendar day, check its timezone selector before changing the timestamp. The epoch value is a single UTC instant; local display rules can shift the visible date.

Copy-ready examples

  • SQL cutoff: created_at_epoch >= 1767225600
  • JavaScript UTC date: new Date(1767225600000).toISOString()
  • ISO output: 2026-01-01T00:00:00.000Z
  • Readable UTC: Thursday, January 1, 2026 00:00:00 UTC

Related epoch date references

For the broader boundary explanation, see 1767225600 as the start of 2026. For general conversion rules, use the epoch to date guide or the epoch to timestamp tool.

Frequently asked questions

What date is 1767225600?

1767225600 is January 1, 2026 at 00:00:00 UTC. It is an epoch-seconds value, not milliseconds.

Is 1767225600 Jan 1 2026 00:00:00 UTC?

Yes. The exact UTC timestamp is 2026-01-01 00:00:00 UTC, and the ISO 8601 form is 2026-01-01T00:00:00.000Z.

What is the millisecond version of 1767225600?

The matching millisecond timestamp is 1767225600000. Use the 13-digit value for JavaScript Date input and browser APIs.

Why can 1767225600 show December 31, 2025 locally?

Timezones west of UTC display the same instant before local midnight, so the local calendar date can be December 31, 2025 even though the UTC date is January 1, 2026.

Related Tools

More free tools for developers debugging timestamps, schedules, and text changes.