Unix Timestamp 1000000

What does the timestamp 1000000 mean?

1,000,000 is one of those round, memorable Unix timestamps developers actually notice. It marks the first time Unix time crossed one million seconds, landing on Monday, January 12, 1970 at 13:46:40 UTC. Below is everything you need to read, convert, and reuse this exact value.

One million seconds after the epoch falls less than two weeks into 1970. It is a useful illustration of scale: a million seconds is only about 11.5 days, whereas a billion seconds is nearly 32 years.

Why 1000000 matters

One million seconds after the epoch is 13:46:40 UTC on Monday, January 12, 1970, and the main reason to look it up is to calibrate your intuition. A million seconds is 11 days, 13 hours, 46 minutes and 40 seconds; a billion seconds is a little under 31.7 years; a trillion seconds is roughly 31,700 years. Those three numbers, each a thousand times the last, span the gap between a fortnight, a working life and the whole of recorded history, which is why the difference between a nine-digit and a ten-digit timestamp matters more than it looks. The value also shows how young Unix was when its clock passed a million. In January 1970 the system existed only on a PDP-7 at Bell Labs; the PDP-11 port that carried it beyond the lab and the first edition of the manual were still months away, so no machine actually observed this second as Unix time while it was happening. In milliseconds, 1,000,000 is just 16 minutes and 40 seconds past the epoch, the kind of discrepancy that trips up anyone who mixes JavaScript's millisecond clock with a seconds-based API.

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,000,000 seconds is the same instant as 1,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 Monday, January 12, 1970 at 13:46:40 UTC, which is a Monday. In the two most common machine-readable formats it is 1970-01-12T13:46:40Z (ISO 8601) and Mon, 12 Jan 1970 13:46:40 +0000 (RFC 2822). All of these describe one and the same moment in time; they differ only in notation.

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

// JavaScript
const ts = 1000000;
const date = new Date(ts * 1000);   // JS uses milliseconds
console.log(date.toUTCString());    // Mon, 12 Jan 1970 13:46:40 GMT
console.log(date.toISOString());    // 1970-01-12T13:46:40Z

# Python 3
from datetime import datetime, timezone
ts = 1000000
print(datetime.fromtimestamp(ts, tz=timezone.utc))
# 1970-01-12 13:46:40+00:00

# Bash / GNU date
date -u -d @1000000
# Mon, 12 Jan 1970 13:46:40 UTC

# macOS / BSD date
date -u -r 1000000

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

0 — The Unix EpochThursday, January 1, 197086400 — One Day After the EpochFriday, January 2, 19701000000000 — One Billion SecondsSunday, September 9, 20011111111111 — Repdigit Timestamp 1111111111Friday, March 18, 2005