Technical and media time

NTP Timestamp Converter

Convert between UTC time and the NTP seconds epoch.

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 between UTC time and the NTP seconds epoch.

The NTP Timestamp Converter builds a readable value from UTC timestamp and Fraction digits; Keep Fraction digits beside the copied output.

InterfaceTechnical console
OutputReadable and copyable values

Instructions

How to use this calculator

Set UTC timestamp and Fraction digits from the NTP Timestamp Converter source record, then compare Fraction digits with the required technical convention.

  1. Set UTC timestamp and Fraction digits exactly as supplied by the source record.
  2. Build the NTP Timestamp Converter conversion and compare Fraction digits with the copyable output.
  3. Compare the NTP Timestamp Converter reference with the Fraction digits definition or convention.

Calculation

Method used

NTP seconds equal Unix seconds plus the epoch difference from 1900 to 1970.

NTP seconds = Unix seconds + 2,208,988,800.

The NTP Timestamp Converter relates UTC timestamp and Fraction digits to the converted value; keep the Fraction digits precision or unit convention.

Calculation method last reviewed: June 21, 2026.

Verification

References

Reference and calculation method reviewed: June 21, 2026.

Worked scenario

Example calculation

Example: A UTC instant expressed as Unix time becomes an NTP value by adding the fixed epoch difference.

Compare the NTP Timestamp Converter worked value with Fraction digits, then inspect its precision and format.

Interpretation

Validating the generated output

The displayed scalar is a simplified seconds value and not a complete NTP packet timestamp or era decoder.

Inspect the NTP Timestamp Converter output against Fraction digits before sending its unit, epoch, or syntax elsewhere.

Boundaries

Important edge cases and limitations

Era rollover, packet fields, network delay, precision, and leap indicators are not decoded.

Change the NTP Timestamp Converter convention when Fraction digits uses another epoch, precision, or syntax rule.

Input audit

Checklist for this calculation

  • Inspect the NTP Timestamp Converter unit or epoch in UTC timestamp and Fraction digits.
  • Compare Fraction digits with the NTP Timestamp Converter copyable output.
  • Compare the NTP Timestamp Converter reference with the Fraction digits date and use case.

Questions

Frequently asked questions

What happens at the NTP era rollover?

The 32-bit seconds field repeats, so external era context is needed to identify the intended date.

When should RFC 5905: Network Time Protocol Version 4 be checked for the

Compare RFC 5905: Network Time Protocol Version 4 with Fraction digits whenever the NTP Timestamp Converter boundary affects a decision. Keep its version or access date beside UTC timestamp.

When is a previous ntp timestamp converter output no longer comparable?

Another NTP Timestamp Converter run is warranted when UTC timestamp moves, Fraction digits is redefined, or the governing calculation rule changes.

Which convention should UTC timestamp use in the

UTC timestamp identifies the NTP Timestamp Converter source value, while Fraction digits specifies part of its output convention. Confirm both before copying the converted value.