Unix Timestamp 1234567890

What does the timestamp 1234567890 mean?

1,234,567,890 is one of those round, memorable Unix timestamps developers actually notice. It marks the famous sequential timestamp 1234567890, landing on Friday, February 13, 2009 at 23:31:30 UTC. Below is everything you need to read, convert, and reuse this exact value.

Perhaps the most celebrated timestamp of all, 1234567890 spells out a perfect ascending sequence. Parties were held in San Francisco and elsewhere to watch it roll over. It is the single most searched-for "fun" Unix timestamp.

Why 1234567890 matters

No other timestamp has had parties thrown for it in as many cities. 1234567890 arrived at 23:31:30 UTC on Friday, February 13, 2009, which was 3:31:30 in the afternoon in California, and developers gathered in bars and offices from San Francisco to Copenhagen to watch a terminal running date +%s tick through the digits. The appeal is obvious: the ten digits count up in perfect sequence, something that had never happened before in the Unix era and will never happen again. That it landed on a Friday the 13th only added to the fun, and the mainstream technology press covered the moment widely. Beyond the novelty, the value has become a de facto standard in documentation and test suites. Search almost any language's date-parsing examples and you will find 1234567890 used as the sample input, precisely because a reader can verify the digits at a glance. There is a millisecond trap here too: 1234567890 read as milliseconds is a few hours into January 15, 1970, so an example that resolves to 1970 instead of 2009 has almost certainly been fed the wrong unit.

The exact value, every way you need it

A Unix timestamp is a single integer: the count of seconds elapsed since the Unix epoch (midnight UTC on January 1, 1970), ignoring leap seconds. The value 1,234,567,890 seconds is the same instant as 1,234,567,890,000 milliseconds — the form most programming languages expect, since JavaScript, Java, and many databases store time in milliseconds. Written out in full it is Friday, February 13, 2009 at 23:31:30 UTC, which is a Friday. In the two most common machine-readable formats it is 2009-02-13T23:31:30Z (ISO 8601) and Fri, 13 Feb 2009 23:31:30 +0000 (RFC 2822). All of these describe one and the same moment in time; they differ only in notation.

How to convert 1234567890 in code

Turning this timestamp into a human-readable date takes a single expression in most languages. In JavaScript, remember to multiply by 1000 because Date works in milliseconds: new Date(1234567890 * 1000).toUTCString(). Here are the equivalents in three common environments:

// JavaScript
const ts = 1234567890;
const date = new Date(ts * 1000);   // JS uses milliseconds
console.log(date.toUTCString());    // Fri, 13 Feb 2009 23:31:30 GMT
console.log(date.toISOString());    // 2009-02-13T23:31:30Z

# Python 3
from datetime import datetime, timezone
ts = 1234567890
print(datetime.fromtimestamp(ts, tz=timezone.utc))
# 2009-02-13 23:31:30+00:00

# Bash / GNU date
date -u -d @1234567890
# Fri, 13 Feb 2009 23:31:30 UTC

# macOS / BSD date
date -u -r 1234567890

If you would rather not write code at all, the Epoch Converter is pre-loaded with 1234567890 so you can see it converted instantly and tweak the value live.

How long ago (or how far away) is it?

The headline near the top of this page updates every time you load it, computing the gap between 1234567890 and your current clock in real time so it never goes stale. To measure the span between this timestamp and any other date precisely — in years, months, weeks, days, or business days — use the Date Duration Calculator. To watch a future moment tick down second by second, the Countdown Timer can target this exact instant.

Why timestamps matter

Storing time as a plain integer of seconds is wonderfully unambiguous: there is no time zone, no daylight saving, and no locale to misinterpret. Two servers anywhere on Earth agree on what 1234567890 means. That is why logs, databases, JWTs, file metadata, and APIs lean on Unix time so heavily. The trade-off is that the number is not human-friendly at a glance — which is exactly the gap a reference like this page fills.

Related timestamps

Other notable Unix timestamps worth a look:

1000000000 — One Billion SecondsSunday, September 9, 20011111111111 — Repdigit Timestamp 1111111111Friday, March 18, 20051300000000 — Round Timestamp 1.3 BillionSunday, March 13, 20111400000000 — Round Timestamp 1.4 BillionTuesday, May 13, 2014