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: .

Loading time …

--:--:--

Measuring the offset in a moment.

Your device clock: --:--:--

Large display = corrected time. The check runs automatically when the page opens, only against our own server.

My Toolbox

Result

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:

  1. It notes your device time when a request leaves and when the answer arrives.
  2. It works out a window for the offset. The server stamped the answer somewhere in between, and that stamp stands for a full second.
  3. 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.
  4. 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.

Measured offset and error margin in simulated runs
True offsetRound tripSamplesResult
1.5 s fast40 ms11.92 s fast, ±0.52 s
1.5 s fast40 ms81.50 s fast, ±0.10 s
1.5 s fast120 ms81.57 s fast, ±0.17 s
1.5 s fast400 ms81.44 s fast, ±0.36 s
2.3 s slow60 ms82.33 s slow, ±0.09 s
0 s800 ms80.04 s fast, ±0.64 s

Common mistakes when checking a clock

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

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

As of: · Editorial policy

Related tools