4294967295 is a Unix timestamp in seconds. It represents 2106-02-07T06:28:15Z.
The same instant in milliseconds
JavaScript Date expects milliseconds, so the equivalent value is 4294967295000.
const seconds = 4294967295;
const date = new Date(seconds * 1000);
console.log(date.toISOString());
// 2106-02-07T06:28:15.000Z
The common wrong-unit result
Passing 4294967295 directly to new Date() treats it as milliseconds and produces 1970-02-19T17:02:47.295Z. 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, find 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 4294967295?
- A: 4294967295 in Unix seconds is 2106-02-07T06:28:15.000Z — Sunday, February 7, 2106 at 06:28:15 UTC.
- Q: What is 4294967295 in milliseconds?
- A: 4294967295000 milliseconds is the same instant — the form JavaScript Date and Java Instant expect.
- Q: Why does new Date(4294967295) show 1970?
- A: JavaScript Date takes milliseconds. The seconds value treated as milliseconds points to early 1970. Use new Date(4294967295 * 1000) instead.
- Q: How do I convert 4294967295 in shell?
- A: Linux: date -u -d @4294967295. macOS: date -u -r 4294967295. Both return the UTC date.