Unix (s):1782526626
Unix (ms):1782526626146
ISO 8601:2026-06-27T02:17:06.146Z
live

Unix Timestamp Converter

Paste anything
✓ detected: unix timestamp (seconds)

Standard formats

unix timestamp (seconds)
1742169600
unix timestamp (milliseconds)
1742169600000
iso 8601 (utc)
2025-03-17T00:00:00.000Z
iso 8601 (local, no Z)
2025-03-17T00:00:00
rfc 2822 (email/http)
Mon, 17 Mar 2025 00:00:00 +0000
human readable
Monday, 17 March 2025, 00:00:00 UTC

Timezones

UTC
17 Mar 2025, 00:00:00
UTC
17 Mar 2025, 00:00:00
—

Platform-specific formats

windows filetime
133866432000000000
apple cocoa time
763862400
excel serial date
45733.00000
ntp timestamp
3951158400
gps timestamp
Week 2358, ToW 86400s
.net datetime ticks
638777664000000000
webkit timestamp
13386643200000000
tai timestamp
1742169637
(UTC +37s, as of 2017)
julian date
2460751.50000
modified julian date (mjd)
60751.00000
lilian date
161591
unix day
20164

ABOUT THIS TIMESTAMP

Unix timestamp 1742169600 represents Monday, 17 March 2025 at 00:00:00 UTC. In milliseconds it is 1742169600000. This moment falls on day 76 of 2025, in week 11. The ISO 8601 representation is 2025-03-17T00:00:00.000Z. The Windows FILETIME equivalent is 133866432000000000. The Apple Cocoa timestamp is 763862400. The Excel serial date is 45733.00000. The NTP timestamp is 3951158400. The Modified Julian Date is 60751.00000. The Unix Day number is 20164.

DAY OF WEEK
Monday
DAY OF YEAR
76 of 365
WEEK NUMBER
Week 11
UNIX DAY
20164
LEAP YEAR
No
DAYS FROM TODAY
467 days ago
UTC OFFSET FROM NOW
-467 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.