Interpret a UUID

Back

Your input:                      e09a6603-9e05-8c00-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:e09a6603-9e05-8c00-87ea-5ce32bd83b97
URI:                             uuid:e09a6603-9e05-8c00-87ea-5ce32bd83b97
Microsoft GUID syntax:           {E09A6603-9E05-8C00-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xe09a6603, 0x9e05, 0x8c00, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.298548753864404916320394671562912447383
As OID (Microsoft):              1.2.840.113556.1.8000.2554.57498.26115.40453.35840.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.16184360376631397376.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3768215043.2651163648.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.57498.26115.40453.35840.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xe09a66039e05c0007ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xe09a6603]
Custom data block2 (16 bit):     [0x9e05]
Custom data block3 (12 bit):     [0xc00]
Custom data block4 (14 bit):     [0x07ea]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3

Random 16 bits:                  [0xe09a] 0b1110000010011010
Milliseconds:                    [0x66] 400 (deviation -2ms..2ms)
Seconds:                         [0x03] 3
Minute of day:                   [0x059e] 1438 (23:57)
Day of year:                     [0x00c] 12 (Day=12, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-12 23:57:03'400 (deviation -2ms..2ms)