Time.ms
Heure atomique précise
Aller au contenu principal

Précision et confiance

Fonctionnement de la précision Time.ms

Time.ms shows exact current time by calibrating your browser against a network time reference, then displaying measured delay and estimated uncertainty.

Live Calibration

Each sync sample records request start, response return, and the server timestamp.

Delay Compensation

The app adds half the measured round-trip time to the server timestamp as a practical browser-side estimate.

Transparent Uncertainty

Accuracy is shown as an estimate based on the latest network delay.

What the displayed time represents

After a successful calibration, Time.ms anchors the calibrated timestamp to the browser monotonic clock so the display can update smoothly.

How network delay affects precision

Round-trip time measures a request leaving your browser and the response coming back. Half of RTT is used as delay compensation, while the accuracy estimate remains conservative.

Why Time Offset is stable now

Time Offset is the difference between calibrated time and your device clock at the latest accepted sync sample. It updates only after a new sync is accepted.

What happens when a source is unavailable

The site first tries a protected first-party time endpoint. If unavailable, the browser falls back to client-side public time metadata so the UI keeps working.

Privacy boundaries

Time synchronization does not require an account or precise device location. Browser geolocation is optional and only used after you click the device location control.

estimated accuracy = round-trip time / 2 + browser timing allowance

The allowance keeps the value conservative and easy to understand in normal browser conditions.

Lire l’état de synchro

RTT
Lower round-trip time usually means a tighter estimate.
Accuracy
A conservative browser-side estimate derived from the latest accepted sync.
Offset
How far your device clock was from calibrated time at the latest accepted sync sample.

FAQ précision

Why does Time.ms show an accuracy estimate?

Browser synchronization depends on live network delay. Time.ms measures that delay and shows a conservative estimate.

Why can my Time Offset change after a new sync?

The displayed offset updates when Time.ms accepts a new calibration sample.

Does Time.ms need precise device location?

No. Exact time synchronization does not require device geolocation.