1893456000 is a Unix timestamp in seconds. It represents 2030-01-01T00:00:00Z.
The same instant in milliseconds
JavaScript Date expects milliseconds, so the equivalent value is 1893456000000.
const seconds = 1893456000;
const date = new Date(seconds * 1000);
console.log(date.toISOString());
// 2030-01-01T00:00:00.000Z
The common wrong-unit result
Passing 1893456000 directly to new Date() treats it as milliseconds and produces 1970-01-22T21:57:36.000Z. That date is not a parsing mystery; it is a seconds-versus-milliseconds mismatch.
Use it in a range query
A single timestamp is useful for a fixture or known event. For a date range, calculate the start and next boundary in the intended timezone, then use a half-open comparison: greater than or equal to the start and less than the next start.
Frequent questions:
- Q: What date is Unix timestamp 1893456000?
- A: 1893456000 in Unix seconds is 2030-01-01T00:00:00.000Z — Tuesday, January 1, 2030 at 24:00:00 UTC.
- Q: What is 1893456000 in milliseconds?
- A: 1893456000000 milliseconds is the same instant — the form JavaScript Date and Java Instant expect.
- Q: Why does new Date(1893456000) show 1970?
- A: JavaScript Date takes milliseconds. The seconds value treated as milliseconds points to early 1970. Use new Date(1893456000 * 1000) instead.
- Q: How do I convert 1893456000 in shell?
- A: Linux: date -u -d @1893456000. macOS: date -u -r 1893456000. Both return the UTC date.