The Unix timestamp 1800000000 is 15 January 2027 at 08:00:00 UTC. It is the number of seconds elapsed since midnight UTC on 1 January 1970.
Calculation assumptions
Converts a Unix timestamp in seconds or milliseconds to a UTC date and time, or a UTC date to a timestamp. Dates are always read as UTC, not your local time.
Unix time = seconds since 1970-01-01 00:00:00 UTC (13 digits = milliseconds)
Converts a Unix timestamp in seconds or milliseconds to a UTC date and time, or a UTC date to a timestamp. Dates are always read as UTC, not your local time.
All amounts use the same currency of your choice. These are estimates, not measurements or offers.
How to use this calculator
Paste a timestamp from a log, a database or an API to see which date it is, or type a date to get its timestamp. Seconds (10 digits) and milliseconds (13 digits) are accepted, such as the values returned by Date.now() in JavaScript.
Worked example
1,800,000,000 seconds ÷ 86,400 = 20,833.33 days since 1970.
20,833 whole days lead to 15 January 2027.
The remaining 0.33 of a day is 8 hours: 08:00:00 UTC.
Example result
ISO 8601 date (UTC)
2027-01-15T08:00:00.000Z
Timestamp (seconds)
1800000000
Interpreting the result
The result is in UTC, so add or subtract your time zone offset. If the number has 13 digits it is in milliseconds and the tool detects it. Systems that store time in a signed 32-bit integer will fail on 19 January 2038, the so-called year 2038 problem.
Frequently asked questions
How do I get the current timestamp?
On Linux or macOS, date +%s; in JavaScript, Math.floor(Date.now() / 1000); in Python, int(time.time()).
Do timestamps have a time zone?
No: they always count from 1970 in UTC. The time zone only applies when the date is displayed.
What is the year 2038 problem?
Signed 32-bit counters reach their maximum, 2147483647, on 19 January 2038 at 03:14:07 UTC. Modern systems use 64 bits.