How Accurate Are Phone Clocks?

Q: How accurate is my phone's clock?

When connected to a network, most smartphones are accurate to within 1-10 milliseconds of true time. When offline, the phone relies on its internal quartz oscillator, which can drift by several seconds per day.

Q: Can a phone be wrong by hours?

A phone's time display can be wrong by hours if you manually set an incorrect time zone or if automatic time zone detection fails. The underlying clock mechanism itself is unlikely to drift by hours unless the device has been offline for an extended period.

Smartphone time accuracy — milliseconds from the network, seconds when offline

Your smartphone is one of the most accurate timekeeping devices you own — when it has a network connection. Most people never think about whether their phone's clock is correct, yet the entire modern experience of synchronized time depends on a sophisticated system of network protocols, time servers, and atomic clock references working silently in the background.

The Short Answer

1–10 ms

Typical smartphone accuracy when connected to a network

When your phone is connected to a cellular or Wi-Fi network and has automatic time enabled, it is accurate to within roughly 1 to 10 milliseconds (thousandths of a second) of the true time. This is accurate enough for virtually every consumer purpose and is maintained automatically without any action from you.

When your phone is offline, however, it falls back on its internal quartz oscillator, which can drift by several seconds per day. A phone left in airplane mode for a week may be off by 10–20 seconds or more.

How Your Phone Keeps Time

Every smartphone contains a small quartz crystal oscillator — the same fundamental technology found in a quartz wristwatch. This crystal vibrates at a precise frequency (typically 32,768 Hz) when powered, and a tiny electronic circuit divides this frequency down to produce a one-second pulse. This is your phone's local clock.

But a quartz crystal alone is not accurate enough for the demands of modern smartphones. GPS navigation, two-factor authentication, encrypted web browsing, financial transactions, and network communication all require precise, consistent time. If your phone's clock drifts by even a second, it could compromise security certificates, break HTTPS connections, or produce incorrect GPS positioning.

To solve this, your phone periodically synchronizes its clock over the network using the Network Time Protocol (NTP).

The Network Time Protocol (NTP)

NTP is the protocol that keeps the internet's clocks in sync. Developed by David L. Mills in 1985, NTP is one of the oldest internet protocols still in active use. It works by exchanging timestamped messages between a client (your phone) and a server, then calculating the round-trip delay to estimate the correct time.

How NTP Works

Request: Your phone sends a timestamped message to a configured NTP server
Response: The server replies with its own timestamp and the server's time
Calculation: The phone measures the round-trip delay and calculates the offset between its clock and the server
Correction: The phone adjusts its clock by the calculated offset, either jumping to the correct time or gradually slewing (speeding up or slowing down) the clock to avoid jarring jumps

NTP accounts for network latency by measuring the round-trip time of each message exchange. If the phone and server are separated by 50 milliseconds of network latency, NTP estimates that the true time is approximately half the round-trip delay ahead of the server's response. This allows NTP to achieve accuracy well below the raw network latency.

NTP Server Hierarchy

NTP uses a hierarchical system of time servers, organized into strata (layers). Each stratum represents one step removed from a reference clock:

Stratum 0 — High-precision reference clocks: cesium atomic clocks, GPS receivers, radio time signals (WWVB, DCF77). These are the ultimate source of accurate time.
Stratum 1 — Primary time servers directly connected to stratum 0 devices. These are operated by national laboratories, universities, and large technology companies.
Stratum 2 — Secondary servers that synchronize to stratum 1 servers. Most consumer devices, including smartphones, synchronize to stratum 2 or stratum 3 servers.
Stratum 3–15 — Additional layers of hierarchy. Each additional stratum adds a small amount of uncertainty, but the system is designed so that even stratum 15 servers are accurate to within a few hundred milliseconds.

Apple, Google, and Microsoft each operate their own NTP server pools that their smartphones and operating systems use by default. These servers are distributed worldwide and are synchronized to stratum 0 and stratum 1 references.

Phone vs. Atomic Clock: The Accuracy Gap

To put smartphone accuracy in perspective, consider the difference between your phone and a cesium atomic clock:

Smartphone (online): Accurate to ~1–10 milliseconds. Errors accumulate between syncs and during network transmission.
Smartphone (offline): Accurate to ~1–5 seconds per day. The quartz crystal drifts due to temperature, aging, and vibration.
Cesium atomic clock: Accurate to ~1 second in 300 million years. The reference frequency is a property of the cesium atom itself.

Despite this enormous gap, the NTP system effectively bridges it. Your phone doesn't need to be as accurate as an atomic clock — it just needs to know when it's wrong and correct itself. By periodically querying NTP servers that are themselves synchronized to atomic clocks, your phone maintains accuracy that is more than sufficient for all everyday purposes.

To learn more about the atomic clocks that underpin global time, see our guide to atomic clocks.

Factors That Affect Phone Time Accuracy

Network Conditions

Slow or unreliable network connections can delay NTP synchronization or prevent it entirely. On congested Wi-Fi networks or in areas with poor cellular coverage, the round-trip time of NTP messages increases, which reduces accuracy. However, NTP's delay compensation algorithms are robust enough to handle most real-world network conditions.

Temperature and Environment

Quartz crystals are sensitive to temperature. A phone left in a hot car or in freezing winter conditions may experience increased clock drift between NTP syncs. The effect is usually small — a few milliseconds per day — but it accumulates when the phone is offline.

Operating System Behavior

Both iOS and Android adjust their NTP sync frequency based on conditions. When the phone first connects to a network, it syncs immediately. While connected, it typically syncs every few hours. When the phone restarts, it syncs before allowing time-dependent operations like SSL certificate validation. Some Android implementations also use a "step" correction (jumping the clock) for large offsets and a "slew" correction (gradually adjusting) for small offsets.

Manual Time Settings

If a user manually sets the time or time zone, the phone will not override that choice with NTP data. This is the most common cause of incorrect time on smartphones. Enabling "Set Automatically" for both date/time and time zone in your phone's settings ensures the best accuracy.

How to Check Your Phone's Time Accuracy

You can verify your phone's clock against an NTP server using various apps or by visiting a time-checking website. Sites like how to check exact time provide web-based tools that account for network latency to give you a more accurate reading than simply comparing your phone to a wall clock.

For most users, the simplest check is: enable automatic date and time, enable automatic time zone, and ensure location services are on. If all three are enabled and your phone is connected to a network, your clock is almost certainly accurate to within a few milliseconds.

Tips for the Most Accurate Phone Time

Enable automatic time synchronization — In Settings > Date & Time (Android) or Settings > General > Date & Time (iOS), turn on "Set Automatically."
Enable automatic time zone — This ensures your phone uses the correct zone based on your location.
Keep location services enabled — Time zone detection relies on your GPS or network location. Without it, the phone may use the wrong zone.
Maintain a network connection — NTP syncs require internet access. A phone in airplane mode for days will drift.
Restart periodically — Phones often force an NTP sync on boot, correcting any accumulated drift.

Why Phone Time Matters More Than You Think

Accurate time on your phone is not just about being on time for appointments. It underpins security, communication, and data integrity:

HTTPS/TLS certificates — Encrypted web connections use certificates with validity windows. If your clock is wrong, valid certificates may appear expired or not-yet-valid, breaking secure connections.
Two-factor authentication — Time-based one-time passwords (TOTP) like Google Authenticator depend on both the phone and the server having synchronized clocks. A drift of more than 30 seconds can cause codes to be rejected.
GPS and location services — GPS receivers calculate position by measuring signal travel time from satellites. Accurate time is essential for accurate positioning.
Messaging and social media — Message timestamps, "last seen" indicators, and event ordering all rely on consistent time across devices.
Financial transactions — Banking apps and payment services timestamp transactions for fraud detection and regulatory compliance.

How Phones Compare to Other Clocks

A phone's timekeeping falls between consumer quartz clocks and networked computers. A quartz wristwatch may drift by 15 seconds per month. A desktop computer running NTP typically achieves accuracy within a few milliseconds, similar to a phone. A GPS receiver with a good antenna achieves microsecond accuracy. And at the top of the hierarchy, cesium atomic clocks achieve nanosecond-level accuracy.

For a broader understanding of how different clocks compare, see our guide on how clocks work.

Explore Related Topics

Atomic Clocks — The precise references behind all network time
How to Check Exact Time — Tools and methods for verifying your clock
How Do Clocks Work? — From pendulums to quartz to atomic

Frequently Asked Questions

How accurate is my phone's clock?

When connected to a network with automatic time enabled, most smartphones are accurate to within 1–10 milliseconds of true time. When offline, the phone relies on its internal quartz oscillator, which can drift by several seconds per day depending on temperature and device age.

How do phones sync their time?

Smartphones use the Network Time Protocol (NTP) to synchronize with time servers on the internet. These servers are ultimately synchronized to atomic clocks. The phone periodically contacts an NTP server to correct any drift in its local clock, typically every few hours while connected.

Can a phone be wrong by hours?

A phone's time display can show the wrong hour if you have manually set an incorrect time zone or if automatic time zone detection fails. The underlying clock mechanism itself is unlikely to drift by hours unless the device has been offline for an extended period. Enabling automatic date, time, and time zone settings usually prevents this.

Why is my phone showing the wrong time?

Common causes include: automatic time zone is disabled, location services are turned off (preventing zone detection), NTP sync is blocked by network settings, or the device has been offline for a long time. Checking your date, time, and time zone settings and enabling automatic options usually resolves the issue.