What is GPS Time?

GPS time is a time scale maintained by the atomic clocks of satellites and ground control stations of the Global Positioning System (GPS). It consists of a count of weeks and seconds of the week since 0 hours (midnight) Sunday 6 January 1980.

GPS time is a timescale used by the GPS system.

GPS time is a continuous time scale and does not adjust for leap second insertions. It therefore diverges from UTC at the introduction of each leap second.

UTC and Local Time Scales

Time is represented in different ways. Local time is the current time in your locale or region. It is affected by your locations time zone and daylight saving time.

Local time is calculated from UTC time, but is adjusted for time zone and daylight saving offsets.

UTC, or Universal Coordinated Time, is not affected by time zones or daylight saving. It is the same anywhere on Earth, regardless of location. UTC is periodically adjusted to acommodate leap second insertions.

The GPS Atomic Time Scale

The GPS system consists of a constellation of Earth orbiting satellites. Each satellite is fitted with a highly accurate atomic clock, which is periodically synchronized by a ground control station located at USNO, Colorado.

GPS time is the atomic time scale maintained by GPS satellites and the ground control stations used to synchronize the GPS system.

The GPS timescale is a count of weeks and seconds of the week.

The time scale is a count of the number of weeks, and seconds of the current week, since an epoch. The start epoch was 0 hours (midnight) Sunday 6-Jan-1980, when GPS time was 0.

GPS time is continuous and is not adjusted to take account of leap seconds. As leap seconds are introduced over time, GPS time diverges further and further from UTC. As of March 2019, the GPS time scale is 18 seconds ahead of UTC.

In order to be more useful for timing applications, GPS messages contain an offset between GPS and UTC time which allows current UTC time to be calculated by a low-cost ground based receiver.

GPS-UTC Offset

GPS time progresses uniformly, it is unaffected by leap seconds. Therefore, at the introduction of each leap second, it diverges from UTC.

On 1 January 1980, GPS and UTC time were the same, the table below shows the divergence of GPS time from UTC since then.

Date             GPS-UTC Offset 
                 (seconds)
1 January 1980   0
1 July 1981      1
1 July 1982      2
1 July 1983      3
1 July 1985      4
1 January 1988   5
1 January 1990   6
1 January 1991   7
1 July 1992      8
1 July 1993      9
1 July 1994      10
1 January 1996   11
1 July 1997      12
1 January 1999   13
1 January 2006   14
1 January 2009   15
1 July 2012      16
1 July 2015      17
1 January 2017   18

GPS Week Number Rollover

The GPS system maintains time as a count of weeks since 6 January 1980. It stores the week number in a 10-bit register.

However, a binary 10-bit register can only count up to 1024 before it rolls over back to 0. Therefore, every 1024 weeks, or 19.7 years, the week number register will revert to 0 beginning a new epoch.

The first epoch was the start count, 6 January 1980, the second was 21 August 1999, the next epoch is 6 April 2019.

Some older GPS receivers may therefor revert back to 21 August 1999 on 6 April 2019. This is known as the GPS week number rollover issue.

Hard Coded GPS Week Number

Many GPS receivers hard code the GPS week number epoch start date to match the firmware release date. This means that the GPS week number rollover for the receiver will take place exactly 19.7 years after the firmware date.

Other GPS receivers allow a message to be sent to the receiver to adjust the epoch start date manually. In this manner, provided a new epoch start date is periodically set, a rollover will be avoided.

The 13-Bit GPS Week Number Upgrade

The GPS system is currently undergoing a multi-billion dollar improvement and upgrade program.

As part of the upgrade, the updated message types (CNAV and MNAV) will switch to a 13-bit week number. This allows 8192 weeks or 157 years between week number rollovers.

The 13-bit week number upgrade will eliminate future rollover problems.

Common Questions

How Accurate Is GPS Time?

The U.S. Naval Observatory (USNO) maintains UTC time at its control center in Colorado. The control center periodically coordinates the atomic clocks of each GPS satellite.

The GPS system is accurate to 40 nanoseconds.

USNO ensures that the GPS signal has a time transfer accuracy of ≤40 nanoseconds (one thousand-millionths of a second) 95% of the time.

This accuracy is only attainable to a GPS receiver at a fixed location.

Is GPS Time The Same As UTC?

UTC time is linked to the rotation of the Earth. This rotation is not constant, in fact it is generally slightly slowing, and can be affected by events such as Earth quakes.

Periodically, leap seconds are introduced to keep UTC time within one second of the Earths rotation time.

GPS time is not adjusted for leap seconds. Therefore, GPS time diverges from UTC as each leap second is introduced.

However, GPS messages provides a warning of impending leap seconds and also the current GPS-UTC offset, so that UTC time can be accurately calculated by a Earth located receiver.

Related Information

What is the GPS Clock ?
Learn more about GPS Time Servers here.

Additional Resources

http://leapsecond.com/java/gpsclock.htm
https://www.andrews.edu/~tzs/timeconv/timeconvert.php
https://www.nist.gov/pml/time-and-frequency-division/atomic-standards/common-view-gps-time-transfer

Andrew ShintonAbout Andrew Shinton
Andrew Shinton is the joint founder and Managing Director of TimeTools Limited. He has a BSc (Hons) degree in Computer Science. Andrew has over 20 years experience of GPS systems and Network Time Protocol (NTP) in the Time and Frequency Industry.

Share: