SAME DAY. YOUR DIVISION.
Time, in hundreds.
100 hours · 100 minutes · 100 seconds
Mathematical day number: —
One number for date and time
We count from 1 January 0001 at 00:00 UTC: that is day 0. One day contains a million new seconds. For example, 739896.073.069.073 means 739896 + 73/100 + 69/10000 + 73/1000000 = 739896.736973 days.
This clock always uses UTC, regardless of your local zone selection. Its hour may therefore differ, and near midnight its day may differ too. Subtract two mathematical numbers to find the elapsed days; multiply by 86400 for conventional seconds. We follow the system Unix clock, without separately counting leap seconds. The display is truncated to six decimal places; more digits do not guarantee greater accuracy.
THIRTEEN MONTHS · ONE YEAR
Extra days belong to months: day 29 of the final month every year, and day 29 of the first month in leap years. Columns run from Monday to Sunday. The seven-day week continues through every month, extra day and year. Starting point: 1 January 0001 is Monday. Historical dates use the Gregorian rule extended backwards.
One day. A million seconds.
A new second lasts 0.0864 conventional seconds. One hundredth of a new second lasts 0.864 milliseconds.
We first show your device’s system time, then the Atlas server’s time.
How do we calculate date and time?
The year starts on 1 January in your selected zone. Each month has 28 days, except the last, which always has 29. In leap years the first month also has 29 days. Extra days belong to their months and are numbered 029. They have ordinary weekdays too: Friday is followed by Saturday, even at the start of a new year.
The year number stays the same. We use the Gregorian rule: divisible by 4, except years divisible by 100, unless also divisible by 400. This is a personal calendar for everyday life, not a measurement of Earth’s exact orbital position.
The date 013.029 is the final day of the year. The date 001.029 exists only in leap years and corresponds to 29 January. The annual view supports years 0001 to 9999, with the same rule for past and future.
The clock is calculated from the server’s timestamp, not a count of application ticks. Hundredths are shown as fast as the screen can refresh: they are not a claim of atomic accuracy.