Unix (s):1782526199
Unix (ms):1782526199312
ISO 8601:2026-06-27T02:09:59.312Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
999999999
unix timestamp (milliseconds)
999999999000
iso 8601 (utc)
2001-09-09T01:46:39.000Z
iso 8601 (local, no Z)
2001-09-09T01:46:39
rfc 2822 (email/http)
Sun, 09 Sep 2001 01:46:39 +0000
human readable
Sunday, 9 September 2001, 01:46:39 UTC

Timezones

UTC
09 Sept 2001, 01:46:39
UTC
09 Sept 2001, 01:46:39

Platform-specific formats

windows filetime
126444735990000000
apple cocoa time
21692799
excel serial date
37143.07406
ntp timestamp
3208988799
gps timestamp
Week 1131, ToW 6399s
.net datetime ticks
631355967990000000
webkit timestamp
12644473599000000
tai timestamp
1000000036
(UTC +37s, as of 2017)
julian date
2452161.57406
modified julian date (mjd)
52161.07406
lilian date
153001
unix day
11574

ABOUT THIS TIMESTAMP

Unix timestamp 999999999 represents Sunday, 9 September 2001 at 01:46:39 UTC. In milliseconds it is 999999999000. This moment falls on day 252 of 2001, in week 36. The ISO 8601 representation is 2001-09-09T01:46:39.000Z. The Windows FILETIME equivalent is 126444735990000000. The Apple Cocoa timestamp is 21692799. The Excel serial date is 37143.07406. The NTP timestamp is 3208988799. The Modified Julian Date is 52161.07406. The Unix Day number is 11574.

DAY OF WEEK
Sunday
DAY OF YEAR
252 of 365
WEEK NUMBER
Week 36
UNIX DAY
11574
LEAP YEAR
No
DAYS FROM TODAY
9057 days ago
UTC OFFSET FROM NOW
-9057 days

Specialist tools

ABOUT TIMESTAMP CONVERSION

What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since 1 January 1970 00:00:00 UTC -- a moment known as the Unix epoch. It is the most universal way computers store and transmit time because it is a timezone-agnostic integer that requires no calendar logic to compare or sort. Most programming languages, databases, and APIs use Unix timestamps as their internal time representation.

Why are there so many timestamp formats?

Different systems chose different starting points and different units. Windows measures time in 100-nanosecond intervals since 1 January 1601. Apple's frameworks count seconds since 1 January 2001. GPS counts weeks and seconds since 6 January 1980. Excel counts days since 30 December 1899, with an intentional bug that treats 1900 as a leap year for Lotus 1-2-3 compatibility. Converting between these formats requires knowing the offset between each epoch and the Unix epoch, then accounting for differences in unit scale.

What can unixtime.wtf convert?

Paste any timestamp and get instant conversion to 17 formats: Unix seconds, Unix milliseconds, ISO 8601, RFC 2822, human readable, Windows FILETIME, Apple Cocoa time, Excel serial date, NTP timestamp, GPS timestamp, .NET DateTime ticks, WebKit timestamp, TAI, Julian Day Number, Modified Julian Date, Lilian Date, and Unix Day. The specialist tools handle JWT token decoding, cron expression parsing, relative time expressions, and batch log normalisation. All conversions happen client-side -- nothing is sent to a server.