1764581115 is a Unix timestamp in seconds. It represents 2025-12-01T09:25:15Z.
The same instant in milliseconds
JavaScript Date expects milliseconds, so the equivalent value is 1764581115000.
const seconds = 1764581115;
const date = new Date(seconds * 1000);
console.log(date.toISOString());
// 2025-12-01T09:25:15.000Z
The common wrong-unit result
Passing 1764581115 directly to new Date() treats it as milliseconds and produces 1970-01-21T10:09:41.115Z. That date is not a parsing mystery; it is a seconds-versus-milliseconds mismatch.
Use it in a range query
For a known event or fixture, a single timestamp is useful. 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 1764581115?
- A: 1764581115 in Unix seconds is 2025-12-01T09:25:15.000Z — Monday, December 1, 2025 at 09:25:15 UTC.
- Q: What is 1764581115 in milliseconds?
- A: 1764581115000 milliseconds is the same instant — the form JavaScript Date and Java Instant expect.
- Q: Why does new Date(1764581115) show 1970?
- A: JavaScript Date takes milliseconds. The seconds value treated as milliseconds points to early 1970. Use new Date(1764581115 * 1000) instead.
- Q: How do I convert 1764581115 in shell?
- A: Linux: date -u -d @1764581115. macOS: date -u -r 1764581115. Both return the UTC date.