Interpret a UUID

Back

UUID: 
Your input:                      d222572d-0401-8c03-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:d222572d-0401-8c03-87ea-5ce32bd83b97
URI:                             uuid:d222572d-0401-8c03-87ea-5ce32bd83b97
Microsoft GUID syntax:           {D222572D-0401-8C03-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xd222572d, 0x0401, 0x8c03, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.279316185344165158447938166000371383191
As OID (Microsoft):              1.2.840.113556.1.8000.2554.53794.22317.1025.35843.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15141760748025383939.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3525465901.67210243.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.53794.22317.1025.35843.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd222572d0401c0307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xd222572d]
Custom data block2 (16 bit):     [0x0401]
Custom data block3 (12 bit):     [0xc03]
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:                  [0xd222] 0b1101001000100010
Milliseconds:                    [0x57] 341 (deviation -2ms..2ms)
Seconds:                         [0x2d] 45
Minute of day:                   [0x0104] 260 (04:19)
Day of year:                     [0x03c] 60 (Day=1, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-01 04:19:45'341 (deviation -2ms..2ms)