Interpret a UUID

Back

UUID: 
Your input:                      d5600730-d301-8603-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:d5600730-d301-8603-87ea-5ce32bd83b97
URI:                             uuid:d5600730-d301-8603-87ea-5ce32bd83b97
Microsoft GUID syntax:           {D5600730-D301-8603-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xd5600730, 0xd301, 0x8603, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.283624169445728629487597106962311429015
As OID (Microsoft):              1.2.840.113556.1.8000.2554.54624.1840.54017.34307.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15375297034122790403.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3579840304.3540092419.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.54624.1840.54017.34307.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd5600730d30160307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xd5600730]
Custom data block2 (16 bit):     [0xd301]
Custom data block3 (12 bit):     [0x603]
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:                  [0xd560] 0b1101010101100000
Milliseconds:                    [0x07] 27 (deviation -2ms..2ms)
Seconds:                         [0x30] 48
Minute of day:                   [0x01d3] 467 (07:46)
Day of year:                     [0x036] 54 (Day=23, Month=2)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-02-23 07:46:48'027 (deviation -2ms..2ms)