Unix Timestamp 1600000000

What does the timestamp 1600000000 mean?

1,600,000,000 is one of those round, memorable Unix timestamps developers actually notice. It marks the round-number timestamp 1,600,000,000, landing on Sunday, September 13, 2020 at 12:26:40 UTC. Below is everything you need to read, convert, and reuse this exact value.

Falling in September 2020, this clean value is a popular cutoff in date-range filters and a tidy anchor for explaining relative time to people new to Unix timestamps.

Why 1600000000 matters

1,600,000,000 ticked over at 12:26:40 UTC on Sunday, September 13, 2020, in the middle of the first pandemic year, when an unusually large share of the world's developers were working from home and watching such things on a terminal. It happened to arrive one day after Programmers' Day, which in leap year 2020 fell on September 12, the 256th day of the year. Timestamps that begin with 16 cover the period from this date to November 14, 2023, a span that includes the Log4Shell scramble of December 2021 and the start of the current wave of large language models. The value is a popular cutoff in date-range filters precisely because it is round, recent and unambiguous, and it makes a good teaching example: 1.6 billion seconds is 50 years, 256 days, which is easy to check against a calendar. It lies about 74.5 percent of the way through the signed 32-bit range, leaving 17 years, 127 days before the 2038 limit. In hexadecimal it is 0x5F5E1000; in binary its top bit is still clear, which is exactly what keeps it positive in a 32-bit signed field.

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,600,000,000 seconds is the same instant as 1,600,000,000,000 milliseconds — the form most programming languages expect, since JavaScript, Java, and many databases store time in milliseconds. Written out in full it is Sunday, September 13, 2020 at 12:26:40 UTC, which is a Sunday. In the two most common machine-readable formats it is 2020-09-13T12:26:40Z (ISO 8601) and Sun, 13 Sep 2020 12:26:40 +0000 (RFC 2822). All of these describe one and the same moment in time; they differ only in notation.

How to convert 1600000000 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(1600000000 * 1000).toUTCString(). Here are the equivalents in three common environments:

// JavaScript
const ts = 1600000000;
const date = new Date(ts * 1000);   // JS uses milliseconds
console.log(date.toUTCString());    // Sun, 13 Sep 2020 12:26:40 GMT
console.log(date.toISOString());    // 2020-09-13T12:26:40Z

# Python 3
from datetime import datetime, timezone
ts = 1600000000
print(datetime.fromtimestamp(ts, tz=timezone.utc))
# 2020-09-13 12:26:40+00:00

# Bash / GNU date
date -u -d @1600000000
# Sun, 13 Sep 2020 12:26:40 UTC

# macOS / BSD date
date -u -r 1600000000

If you would rather not write code at all, the Epoch Converter is pre-loaded with 1600000000 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 1600000000 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 1600000000 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:

1500000000 — Round Timestamp 1.5 BillionFriday, July 14, 20171577836800 — Start of 2020Wednesday, January 1, 20201640995200 — Start of 2022Saturday, January 1, 20221672531200 — Start of 2023Sunday, January 1, 2023