UUID v1 Timestamp Extractor

Paste a UUID version 1 string into the UUID input field and extract the embedded timestamp — including the UTC date and time, Unix timestamp, and UUID version confirmation. UUID v1 identifiers encode a 60-bit timestamp counting 100-nanosecond intervals since October 15, 1582. Enter your UUID below to decode exactly when it was generated.

Enter a version 1 UUID (xxxxxxxx-xxxx-1xxx-xxxx-xxxxxxxxxxxx format)

hours

Adjust the displayed time to your local timezone. 0 = UTC.

Results

Extracted UTC Date & Time

--

Adjusted Local Date & Time

--

Unix Timestamp (seconds)

--

UUID Version

--

Raw UUID Timestamp (100-ns intervals since 1582-10-15)

--

Milliseconds Since UUID Epoch (1582-10-15)

--

Results Table

Frequently Asked Questions

What is a UUID v1 and why does it contain a timestamp?

UUID version 1 is generated using the current time and the MAC address (or a random node ID) of the machine creating it. The timestamp is a 60-bit value representing the number of 100-nanosecond intervals since October 15, 1582 (the Gregorian calendar epoch). This makes v1 UUIDs time-sortable and allows the creation time to be recovered.

How is the timestamp extracted from a UUID v1?

A UUID v1 has three timestamp fields: time_low (bits 0–31), time_mid (bits 32–47), and time_hi (bits 48–59, with version bits masked out). These are reassembled into a single 60-bit integer. Subtracting the offset 0x01b21dd213814000 (the number of 100-ns intervals between 1582-10-15 and the Unix epoch 1970-01-01) and dividing by 10,000,000 converts it to a Unix timestamp in seconds.

What is the difference between the UUID epoch and the Unix epoch?

The UUID epoch starts on October 15, 1582, the date the Gregorian calendar was adopted. The Unix epoch starts on January 1, 1970. The constant 0x01b21dd213814000 (122192928000000000 in decimal) represents the number of 100-nanosecond intervals between these two dates and is used to convert between them.

Can I extract a timestamp from UUID v4 or other versions?

No. Only UUID version 1 (and version 6/7 in newer drafts) embeds a timestamp. UUID v4 is randomly generated and contains no time information. UUID v3 and v5 are hash-based. This tool will detect the version and alert you if the UUID is not version 1.

How accurate is the extracted timestamp?

UUID v1 timestamps have 100-nanosecond precision theoretically, but in practice the actual resolution depends on the system clock of the generating machine. Most systems generate timestamps with microsecond precision. The raw 100-ns interval count is preserved in the output for full fidelity.

What format should my UUID be in?

Standard UUID format is 32 hexadecimal characters in five groups separated by hyphens: xxxxxxxx-xxxx-1xxx-xxxx-xxxxxxxxxxxx. The '1' in the third group identifies it as version 1. Both uppercase and lowercase hex digits are accepted. Curly-brace wrapped GUIDs (e.g. {xxxxxxxx-xxxx-1xxx-...}) are also supported.

Why might two UUID v1 values generated at the same millisecond have different timestamps?

UUID v1 uses a clock sequence field to handle cases where UUIDs are generated faster than the clock resolution. If multiple UUIDs are created within the same 100-ns window, the clock sequence is incremented, ensuring uniqueness without repeating the same timestamp value.

Is the extracted timestamp in UTC or local time?

The raw extracted timestamp is always in UTC, as UUID v1 timestamps are defined relative to a fixed universal epoch. This tool displays the UTC time by default and lets you apply a timezone offset (in hours) to convert to your local time for convenience.

More Time & Date Tools