Technical and media time

GPS Week and Time-of-Week Converter

Convert UTC time into GPS week and seconds-of-week using an entered offset.

PrivacyRuns in your browser
OutputTechnical console
CostFree to use
Technical console

Enter your details

Adjust the planning assumptions below.

Calculations stay in this browser. Saved inputs and recent results use local browser storage until you clear them.

Your schedule will appear here

Results update after calculation and include a visual timeline, calendar, or dashboard.

Purpose and scope

What this technical calculator produces

Convert UTC time into GPS week and seconds-of-week using an entered offset.

The GPS Week and Time-of-Week Converter keeps UTC timestamp and GPS−UTC offset seconds visible beside the result so the inputs can be checked, saved, and reproduced without reconstructing the calculation later.

InterfaceTechnical console
CategoryTechnical and media time
Result styleHeadline, audit metrics, and visual schedule

Instructions

How to use this calculator

Enter the values requested for the GPS Week and Time-of-Week Converter and replace every sample with the actual schedule, record, or system being analyzed.

  1. Use UTC timestamp and GPS−UTC offset seconds to establish the starting conditions for the GPS Week and Time-of-Week Converter.
  2. Set GPS−UTC offset seconds to match the actual case rather than leaving example assumptions in place.
  3. Run the GPS Week and Time-of-Week Converter with a baseline set of values, then change only one uncertain input at a time when comparing alternatives.

Calculation

Method used

The entered offset is added to elapsed UTC seconds since the GPS epoch before week division.

GPS total seconds = UTC seconds since 1980-01-06 + entered GPS−UTC offset; week = floor(total ÷ 604,800).

The displayed formula makes the role of UTC timestamp and GPS−UTC offset seconds explicit. In the GPS Week and Time-of-Week Converter, keeping those inputs separate helps distinguish a changed assumption from a changed calculation rule.

Calculation method last reviewed: June 20, 2026.

Worked scenario

Example calculation

Example: A modern UTC timestamp with an eighteen-second offset yields a full GPS week and seconds-of-week value.

To audit your own GPS Week and Time-of-Week Converter result, compare UTC timestamp and GPS−UTC offset seconds with the worked scenario. In the GPS Week and Time-of-Week Converter, if the direction or scale looks wrong, verify GPS−UTC offset seconds before changing several inputs at once.

Interpretation

Validating the generated output

The entered offset is essential because GPS time does not insert UTC leap seconds.

Read the headline together with the supporting metrics for UTC timestamp and GPS−UTC offset seconds. A plausible-looking GPS Week and Time-of-Week Converter result can still be unreliable when one of those values uses the wrong unit, date boundary, or local convention.

Visual audit

Checking the technical output

The GPS Week and Time-of-Week Converter technical output is generated from UTC timestamp and GPS−UTC offset seconds. Before relying on the GPS Week and Time-of-Week Converter, compare the human-readable preview with the copyable value, then test that value in a safe environment using the intended platform time zone or syntax rules.

Boundaries

Important edge cases and limitations

The GPS−UTC offset changes after leap seconds; rollover interpretation and receiver behavior are outside the conversion.

If one of these exclusions applies, treat the GPS Week and Time-of-Week Converter output as a baseline and correct GPS−UTC offset seconds or another affected input before recalculating.

Practical use

Recommended workflow

Obtain the applicable offset and rollover context from the receiving system before encoding or decoding data.

Input audit

Checklist for this calculation

  • Confirm the source and units for UTC timestamp and GPS−UTC offset seconds before entering them.
  • Preserve GPS−UTC offset seconds with any saved or shared GPS Week and Time-of-Week Converter result.
  • For the GPS Week and Time-of-Week Converter, review the exclusions above for conditions that could change GPS−UTC offset seconds or the calculation method.
  • Recalculate the GPS Week and Time-of-Week Converter whenever a recorded input or real-world condition changes.

Questions

Frequently asked questions

Why is GPS time ahead of UTC?

GPS time runs continuously while UTC occasionally inserts leap seconds.

Which inputs should be retained with a gps week and time-of-week converter result?

Enter the values requested for the GPS Week and Time-of-Week Converter and replace every sample with the actual schedule, record, or system being analyzed. Retain those values with the method used: The entered offset is added to elapsed UTC seconds since the GPS epoch before week division.

How is the gps week and time-of-week converter result calculated?

The entered offset is added to elapsed UTC seconds since the GPS epoch before week division. GPS total seconds = UTC seconds since 1980-01-06 + entered GPS−UTC offset; week = floor(total ÷ 604,800).

How can the worked example help check the gps week and time-of-week converter?

A modern UTC timestamp with an eighteen-second offset yields a full GPS week and seconds-of-week value. The entered offset is essential because GPS time does not insert UTC leap seconds.

Which conditions still need manual review after using the gps week and time-of-week converter?

The GPS−UTC offset changes after leap seconds; rollover interpretation and receiver behavior are outside the conversion. Obtain the applicable offset and rollover context from the receiving system before encoding or decoding data.

Which entries should be checked first when the gps week and time-of-week converter result seems wrong?

Enter the values requested for the GPS Week and Time-of-Week Converter and replace every sample with the actual schedule, record, or system being analyzed. In the GPS Week and Time-of-Week Converter, begin with the values that define the anchor, duration, interval, or boundary.