Skip to main content
Choose language
English العربية বাংলা Čeština Deutsch Español فارسی Suomi Français हिन्दी Magyar Bahasa Indonesia Italiano 日本語 한국어 Nederlands Polski Português (Brasil) Română Русский Svenska ไทย Türkçe Українська Tiếng Việt 简体中文 繁體中文（香港） 繁體中文（台灣）

Search Time.ms

Opening search…

 Explore Time.ms

Exact time now

Loading date…

Time.ms uses time sources synchronized with the global atomic-clock system, measures and compensates for round-trip network delay, and shows reliable current time with millisecond readout in any time zone.

Syncing • Using device time

Note: the value above does not include device-clock drift accumulated after calibration. This is generally no more than ±1 ms per minute, but the actual rate varies by device. The lowest round-trip latency measured between your browser and the current time-service node. It is typically affected by physical distance, network routing, access quality, and current congestion. Network latency describes the measured connection. It is separate from the estimated time-error range and must not be treated as that range or divided in half. This error does not show whether your device clock is fast or slow.

Time

Time read directly from your device’s system clock. It does not include the correction calculated by Time.ms during calibration
-
-
Calibrated time minus your device time. A positive value means your device clock is behind; a negative value means it is ahead. This is not network latency, time error, or a UTC or time-zone offset
-
Calibrated time minus your device time. A positive value means your device clock is behind; a negative value means it is ahead. This is not network latency, time error, or a UTC or time-zone offset

Time zone

Your device time zone setting
-
Your device time zone offset from UTC
-

Other

Coordinated Universal Time (UTC), the worldwide time reference
UTC time: --:--:--.---
Unix timestamp: seconds since 1970-01-01 00:00:00 UTC
Unix timestamp: -

Network

Your public IPv4 address
-
Your public IPv6 address
-
Your internet service provider
-
Autonomous system number identifying the network operator
-

Location

Network location inferred from your IP address
-
Device location from the browser’s built-in location feature, only after permission

Syncing • Using device time

Note: the value above does not include device-clock drift accumulated after calibration. This is generally no more than ±1 ms per minute, but the actual rate varies by device. The lowest round-trip latency measured between your browser and the current time-service node. It is typically affected by physical distance, network routing, access quality, and current congestion. Network latency describes the measured connection. It is separate from the estimated time-error range and must not be treated as that range or divided in half. This error does not show whether your device clock is fast or slow.

Frequently asked questions

How accurate is Time.ms?
Time.ms calibrates against time sources synchronized with the global atomic-clock system. Each sample combines the browser’s send and receive readings with the server’s receive and send timestamps. The browser then selects several consistent samples with the lowest network round-trip delay. Actual accuracy depends on the current network path and browser timer. With a high-resolution timer and consistent samples, Time.ms can calculate an explicit error range. If the measurements are weaker but still quantifiable, it labels the result as a conservative estimate.
Accuracy guide
What is atomic clock time?
Atomic clocks measure time using stable atomic transitions and are the most accurate timekeeping devices. Atomic-clock ensembles maintained by timing laboratories contribute to Coordinated Universal Time (UTC) worldwide. Time.ms connects to time sources synchronized with the global atomic-clock system, bringing this precision to your browser.
What is RTT (Round-Trip Time)?
RTT measures the request and response journey between your browser and the time server. Time.ms subtracts measured server processing time, uses the resulting network RTT to select the lowest-delay samples, and reports it as a network diagnostic. A lower RTT usually helps, but it is not divided by two to produce the displayed uncertainty.
How does Time.ms detect my location?
Time.ms uses network information associated with your IP address to estimate your country, region, city and time zone without requesting precise device-location permission. IP-based results are approximate and may be wrong. The app uses this context to display local time-zone and UTC-offset information. Time.ms and its infrastructure providers may process this data as described in the privacy policy.
Privacy
How can I make my computer’s clock this accurate?
Start by enabling automatic date and time in system settings, then use Sync now and rerun the clock drift test. Keep the default time source if it works. Open the Network Time Protocol (NTP) setup guide only if synchronization fails or an administrator requires a custom server; Cloudflare is one optional public provider, not the default.
Fix device clockNTP setup
How is the synchronization accuracy calculated?
Each selected low-RTT sample defines a range in which the reference time can fall. Time.ms uses the overlap shared by several consistent samples, then combines half of that range with measured browser and server timing limits. Repeatability determines whether more samples are needed and helps classify result quality. Low-resolution timers or inconsistent samples produce a clearly marked estimate; the number is hidden only when the error range cannot be quantified.
Accuracy guide
Is Time.ms free to use?
Yes. Time.ms is a public service that can be used without charge or registration.

World time at a glance

More cities