NTP timestamp to date
For example, 3913056000 is Mon, Jan 01, 2024, 12:00:00 AM UTC, which is 2024-01-01T00:00:00.000Z in ISO 8601 and 1704067200 in Unix seconds.
Seconds since 1900-01-01T00:00:00Z, the NTP prime epoch. Unix time = NTP − 2208988800.
Detected: NTP timestamp/t/3913056000
Your timezone
UTC · GMT+00:00 · UTC
Mon, Jan 01, 2024, 12:00:00 AM
Common formats
UTC
Mon, Jan 01, 2024, 12:00:00 AM
ISO 8601
2024-01-01T00:00:00.000Z
Unix (seconds)
1704067200
Unix (millis)
1704067200000
Relative
…
An NTP timestamp counts seconds since 1 January 1900, the prime epoch of the Network Time Protocol, so a current value is around 3.9 billion, about 2.2 billion more than the matching Unix time. On the wire it is a 64-bit field: 32 bits of seconds and 32 bits of fraction. Paste the decimal seconds, with a fraction if you have one, or the 16-digit hex form from a packet capture, and parsetime converts it to a date.
Do it with the API
curl https://parsetime.dev/api/t/3913056000?format=ntpThe same conversion as JSON: no key, no signup, permissive CORS. Try this call or read the API docs.
Common questions
- How do I convert an NTP timestamp to Unix time?
- Subtract 2208988800, the number of seconds between 1 January 1900 and 1 January 1970. NTP 3913056000 is Unix 1704067200, midnight UTC on 1 January 2024.
- How do I read the 64-bit hex form?
- The first 8 hex digits are whole seconds since 1900 and the last 8 are the fraction of a second, divided by 2^32. e93c7f0080000000 is 3913056000 seconds plus 0x80000000 / 2^32 = 0.5 s. This page accepts that 16-digit form directly.
- What happens in 2036 when NTP timestamps roll over?
- The 32-bit seconds field reaches its maximum at 06:28:15 UTC on 7 February 2036 and wraps to zero the next second, starting NTP era 1. Decimal values here are read literally, so 4294967296 is the rollover instant. For the hex form this page follows RFC 4330: a high bit of 1 means era 0 and a high bit of 0 means era 1, counted from the rollover.
- Can I convert an NTP timestamp with the API?
- Yes: GET /api/t/3913056000?format=ntp returns the decoded date as JSON. The hex form works the same way, as /api/t/e93c7f0080000000?format=ntp.