Exact time now, with seconds
Find the exact time: this page checks your device clock against our server clock with 8 samples and shows the corrected time with seconds and tenths. In our simulation, the error margin is about ±0.1 s with a 40 ms round trip and about ±0.4 s with 400 ms. Below the time you see how far your clock is ahead or behind.
Source: IETF RFC 9110 – HTTP Semantics, section 6.6.1 “Date” (response timestamp, UTC, NTP sync). Updated: .
How it is calculated
How the offset is measured
Every web server response carries an HTTP Date header stamped to the second, in GMT (RFC 9110, section 6.6.1, read 2 Nov 2026). The page asks our server eight times and goes through these steps:
- It notes your device time when a request leaves and when the answer arrives.
- It works out a window for the offset. The server stamped the answer somewhere in between, and that stamp stands for a full second.
- It overlaps the windows of all samples. The samples fall on different fractions of a second, so the overlap is much narrower than any single window.
- The offset is the middle of the overlap, and the error margin is half its width.
The large display is the corrected time: your device clock plus the measured offset. Your uncorrected device clock is shown below for comparison.
Worked example
A sample leaves at 12:00:04.900 (device clock), the answer arrives at 12:00:04.960, and the server stamp says “12:00:03”. So the server answered between 12:00:03.000 and 12:00:03.999 while the device showed 12:00:04.900 to 12:00:04.960. The device clock is therefore between 0.900 and 1.960 seconds fast. Seven more samples at other fractions of a second shrink this window.
What connection speed does to the margin
These rows come from running our estimator on simulated requests about a second apart. Real results vary with your network.
| True offset | Round trip | Samples | Result |
|---|---|---|---|
| 1.5 s fast | 40 ms | 1 | 1.92 s fast, ±0.52 s |
| 1.5 s fast | 40 ms | 8 | 1.50 s fast, ±0.10 s |
| 1.5 s fast | 120 ms | 8 | 1.57 s fast, ±0.17 s |
| 1.5 s fast | 400 ms | 8 | 1.44 s fast, ±0.36 s |
| 2.3 s slow | 60 ms | 8 | 2.33 s slow, ±0.09 s |
| 0 s | 800 ms | 8 | 0.04 s fast, ±0.64 s |
Common mistakes when checking a clock
- Reading an hour off as drift: a clock that is exactly one hour off is usually in the wrong time zone or daylight saving setting. The offset here compares absolute time, so check the time zone line under the clock. For other places, use the world clock or the time difference calculator.
- Ignoring the margin: “0.2 s fast, ±0.4 s” does not prove your clock is fast. The offset is smaller than the uncertainty.
- Measuring on a shaky connection: on mobile data or a VPN, measure again on a stable network before changing anything.
- Treating a phone as the reference: a second device has its own error. Comparing two screens by eye also adds your reaction time, which the stopwatch lets you feel for yourself.
- Mixing up clock time and timestamps: a log entry in Unix time has no time zone. The Unix timestamp converter turns it into a date.
Why device clocks drift
According to NIST’s Internet Time Service page (read 2 Nov 2026), Windows, macOS and Linux can set the system clock automatically by querying an NTP server in the background. If automatic time is switched off or the computer has been offline for a long time, nothing corrects the clock and it drifts.
Limits
- The reference is our server’s clock, not an atomic clock directly. RFC 9110 says a clock implementation ought to synchronize with UTC via NTP or a similar protocol; if the server were off anyway, the result would be off too.
- A server stamp only has whole seconds, so this page cannot reach the precision of a direct NTP sync.
- Accuracy depends on your connection’s round-trip time. On unstable networks the window gets wider, and the page always shows the error margin.
- The page cannot set your system clock. To fix it, turn on “Set time automatically” in your system settings.
Frequently asked questions
How accurate is the time shown?
It is as accurate as the error margin on screen, usually a few tenths of a second. The margin shrinks on a fast, stable connection and grows on mobile data or VPN.
Is this an atomic clock?
No. The reference is our server clock, which is meant to be synchronized with Coordinated Universal Time (UTC). The page measures how far your device is off from it.
Why is my clock fast or slow?
Usually automatic time is turned off or the device was offline for a long time. Turn on “Set time automatically”, then measure again.
My clock is exactly one hour off. Why does the page say it is right?
Your device probably has the wrong time zone or daylight saving setting. The check compares absolute time, so a wrong time zone does not count as an offset; look at the time zone line under the clock.
Does it show the time with seconds?
Yes, with seconds and tenths of a second. “Full screen” fills the whole display, for example in a classroom.
What data is sent?
Only eight short requests to our own server; the page reads the timestamp of the answer. The measurement saves nothing on your device and uses no third-party service.
Sources and legal basis
- IETF RFC 9110 – HTTP Semantics, section 6.6.1 “Date” (response timestamp, UTC, NTP sync)
- MDN: Date HTTP header
As of: · Editorial policy
Related tools
- Time zone meeting plannerPlan a meeting across time zones: pick cities, a date and working hours to see the overlap in every local time, with daylight saving time handled.
- Online StopwatchFree online stopwatch with lap times, fastest/slowest lap and copy-to-clipboard. Keeps running after switching tabs or reloading the page.
- Countdown to a DateFree countdown to any date: days, hours, minutes and seconds left until your event, live and updating every second – shareable as a link or embed.
- What week number is it today?Today’s week number (ISO 8601 and US count), the week of any date, the dates of any week and all week numbers of the year – with ICS export and print.
- Online TimerFree online countdown timer: enter any time or tap a 5, 10 or 15 minute preset, get an alarm when time is up, remaining time in the tab. No sign-up.
- How many days until New Year?Live New Year countdown: days, hours, minutes and seconds until midnight on January 1, plus the weekday of New Year’s Eve and Day through 2029.
- Hindu Festivals 2027Hindu festivals 2027 with dates: Diwali, Holi, Janmashtami, Dussehra, Ganesh Chaturthi, Raksha Bandhan and more – as notified by the Government of India.
- Hindu Festivals 2026Hindu festivals 2026 with dates: Diwali, Holi, Janmashtami, Dussehra, Ganesh Chaturthi, Raksha Bandhan and more – as notified by the Government of India.
- Moon Phase Calendar 2026: Full Moon and New Moon DatesMoon phase calendar 2026 with all 13 full moons and 12 new moons: date, weekday and time, moon sign, a printable monthly view and a calendar file.