Unix (s):1782526334
Unix (ms):1782526334659
ISO 8601:2026-06-27T02:12:14.659Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1142899200
unix timestamp (milliseconds)
1142899200000
iso 8601 (utc)
2006-03-21T00:00:00.000Z
iso 8601 (local, no Z)
2006-03-21T00:00:00
rfc 2822 (email/http)
Tue, 21 Mar 2006 00:00:00 +0000
human readable
Tuesday, 21 March 2006, 00:00:00 UTC

Timezones

UTC
21 Mar 2006, 00:00:00
UTC
21 Mar 2006, 00:00:00
—

Platform-specific formats

windows filetime
127873728000000000
apple cocoa time
164592000
excel serial date
38797.00000
ntp timestamp
3351888000
gps timestamp
Week 1367, ToW 172800s
.net datetime ticks
632784960000000000
webkit timestamp
12787372800000000
tai timestamp
1142899237
(UTC +37s, as of 2017)
julian date
2453815.50000
modified julian date (mjd)
53815.00000
lilian date
154655
unix day
13228

ABOUT THIS TIMESTAMP

Unix timestamp 1142899200 represents Tuesday, 21 March 2006 at 00:00:00 UTC. In milliseconds it is 1142899200000. This moment falls on day 80 of 2006, in week 12. The ISO 8601 representation is 2006-03-21T00:00:00.000Z. The Windows FILETIME equivalent is 127873728000000000. The Apple Cocoa timestamp is 164592000. The Excel serial date is 38797.00000. The NTP timestamp is 3351888000. The Modified Julian Date is 53815.00000. The Unix Day number is 13228.

DAY OF WEEK
Tuesday
DAY OF YEAR
80 of 365
WEEK NUMBER
Week 12
UNIX DAY
13228
LEAP YEAR
No
DAYS FROM TODAY
7403 days ago
UTC OFFSET FROM NOW
-7403 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.