Date | |
---|---|
Saturday 28th of May 2022 06:30:22 AM | UTC |
2022-05-28T06:30:22+0000 | ISO 8601 |
Sat, 28 May 22 06:30:22 +0000 | RFC 822, 1036, 1123, 2822 |
Sat, 28 May 2022 06:30:22 +0000 | RFC 2822 |
2022-05-28T06:30:22+00:00 | RFC 3339 |
Unix time (also known as Epoch time, Posix time, seconds since the Epoch, or UNIX Epoch time) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, minus leap seconds; the Unix epoch is 00:00:00 UTC on 1 January 1970 (an arbitrary date); it is nonlinear with a leap second having the same Unix time as the second before it, and every day is treated as if it contains exactly 86400 seconds. Due to this treatment Unix time is not a true representation of UTC.
The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds (in ISO 8601: 1970-01-01T00:00:00Z). Literally speaking the epoch is Unix time 0 (midnight 1/1/1970), but 'epoch' is often used as a synonym for Unix time. Some systems store epoch dates as a signed 32-bit integer, which might cause problems on January 19, 2038 (known as the Year 2038 problem or Y2038). The converter on this page converts timestamps in seconds (10-digit), milliseconds (13-digit) and microseconds (16-digit) to readable dates.
Human-readable time | Seconds |
---|---|
1 hour | 3600 seconds |
1 day | 86400 seconds |
1 week | 604800 seconds |
1 month (30.44 days) | 2629743 seconds |
1 year (365.24 days) | 31556926 seconds |
On this date the Unix Time Stamp will cease to work due to a 32-bit overflow. Before this moment millions of applications will need to either adopt a new convention for time stamps or be migrated to 64-bit systems which will buy the time stamp a "bit" more time.
Swift |
|
Go |
|
Java |
|
JavaScript |
|
Objective-C |
|
MySQL |
|
SQLite |
|
Erlang |
|
PHP |
|
Python |
|
Ruby |
|
Shell |
|
Groovy |
|
Lua |
|
.NET/C# |
|