Live Calibration
Each sync sample records request start, response return, and the server timestamp.
精度と信頼
Time.ms shows exact current time by calibrating your browser against a network time reference, then displaying measured delay and estimated uncertainty.
Each sync sample records request start, response return, and the server timestamp.
The app adds half the measured round-trip time to the server timestamp as a practical browser-side estimate.
Accuracy is shown as an estimate based on the latest network delay.
After a successful calibration, Time.ms anchors the calibrated timestamp to the browser monotonic clock so the display can update smoothly.
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.
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.
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.
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.
Browser synchronization depends on live network delay. Time.ms measures that delay and shows a conservative estimate.
The displayed offset updates when Time.ms accepts a new calibration sample.
No. Exact time synchronization does not require device geolocation.
Return to exact current time, check device clock drift, or convert UTC, ISO, and Unix values.