Current timestamp
LiveTimestamp → Date
SportDate → Timestamp
CalcCoreWhat is a Unix timestamp
A Unix timestamp (also known as epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC (the "Unix epoch"). It's a standard way of representing date and time as a single integer, widely used in programming, databases, and APIs.
Seconds vs milliseconds
The classic Unix timestamp is measured in seconds. However, JavaScript (via
Date.now()) and some other programming languages use timestamps in
milliseconds for greater precision — that's simply the timestamp in seconds
multiplied by 1000.
Why timestamps are used
- Databases: storing dates as numbers simplifies sorting and comparison.
- APIs: many REST APIs return dates as Unix timestamps.
- Logs and event records: precise recording of an event's moment regardless of time zone.
- Debugging: quickly converting a timestamp from logs into a readable date.
The Year 2038 problem (Y2038)
Older 32-bit systems store the Unix timestamp as a signed 32-bit integer, which will overflow on January 19, 2038 at 03:14:07 UTC. This can cause errors in legacy systems, similar to the Year 2000 problem (Y2K). Modern 64-bit systems don't have this limitation.
The "Date → Timestamp" conversion uses UTC as the base time zone.
FAQ
What is a Unix timestamp?
A Unix timestamp (epoch time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. It's used in programming to store date and time as a single number.
Why is a timestamp sometimes in milliseconds and sometimes in seconds?
The standard Unix timestamp is measured in seconds. However, JavaScript and some other programming languages often use milliseconds (timestamp × 1000) for greater precision.
Is there a Year 2038 problem?
Yes, 32-bit systems that store the timestamp as a signed integer will overflow on January 19, 2038. Modern 64-bit systems don't have this limitation.