Unix timestamp 956100030

Jump to a timestamp:

The following table converts the unix timestamp 956100030 to various other RFC formats:

Standard name	Equivalent
< 956100000 — 956100029	956100031 — 956150000 >
Unix Timestamp:	956100030
ANSIC:	Tue Apr 18 23:20:30 2000 in ANSIC format
UnixDate:	Tue Apr 18 23:20:30 UTC 2000 in Unix Date format
RubyDate:	Tue Apr 18 23:20:30 +0000 2000 in Ruby Date format
RFC822:	18 Apr 00 23:20 UTC in RFC 822
RFC822Z:	18 Apr 00 23:20 +0000 in RFC822Z format
RFC850:	Tuesday, 18-Apr-00 23:20:30 UTC in RFC 850 format
RFC1123:	Tue, 18 Apr 2000 23:20:30 UTC in RFC 1123 format
RFC1123Z:	Tue, 18 Apr 2000 23:20:30 +0000 in RFC 1123Z format
RFC3339:	2000-04-18T23:20:30Z in RFC 3339 format
RFC3339Nano:	2000-04-18T23:20:30Z in RFC 3339 nano format
RFC2822:	Tue Apr 18 23:20:30 +0000 2000 in RFC 2822 format
< 956100000 < 956100029	956100031 — 956150000 >

What is the unix time stamp?

It's the number of seconds since the Unix Epoch. The Unix Epoch starts January 1st, 1970 at UTC, and skips leap seconds. The Unix Epoch is based on a UTC starting point, so does not change in different timezones. Read more on wikipedia.

What happens on January 19, 2038?

In early 2038 the Unix Time Stamp, if uses 32-bit signed integer, will overflow. This is really bad. Older systems will need to upgrade their timestamp storage to cope to avoid failure. Read more on wikipedia.

Go back to the index | See the code