Current unix time / stamp :


For an easy to understand introduction to Unix time, go to the front page. This page contains slightly more esoteric information, as you will find out.

The year 2038 problem

On January 19 2038, Unix time 2147483647, systems still storing Unix time as a signed 32-bit integer will start to malfunction due to an overflow. 2147483647 is simply as high as a signed 32-bit integer can go! The bugs that will result are specific to the way the respective OS or program is using Unix time; they can be lethal shutdowns or harmless GUI errors. This problem is similar to the Y2K incident, and it is therefore variously named the Unix Millennium bug, Y2K38, or simply the year 2038 problem. Fortunately for all of us, most systems are likely to have switched to 64-bit by the year 2038, but you can go scare yourself some more by surfing over to

1000000000th second

Unix time 1000000000 fell on 9th September 2001, 01:46:40 AM (UTC) and was celebrated in by a party held by Danish UNIX User Group in Copenhagen.

1234567890 day!?

Unix time 1234567890 ticked on 13th February of 2009, 11:31:30 PM (UTC). Thanks in part to the success of previous unix time parties, and the efforts of, '1234567890 parties' were held in many major cities around the world.