Interprete a UUID

Back

Your input:                      acd17003-6001-8d0d-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:acd17003-6001-8d0d-87e9-5ce32bd83b97
URI:                             uuid:acd17003-6001-8d0d-87e9-5ce32bd83b97
Microsoft GUID syntax:           {ACD17003-6001-8D0D-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xacd17003, 0x6001, 0x8d0d, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.229714677215711841615642142774211918743
As OID (Microsoft):              1.2.840.113556.1.8000.2554.44241.28675.24577.36109.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12452857604454059277.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2899406851.1610714381.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.44241.28675.24577.36109.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xacd170036001d0d07e95ce32bd83b97]
Custom data block1 (32 bit):     [0xacd17003]
Custom data block2 (16 bit):     [0x6001]
Custom data block3 (12 bit):     [0xd0d]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xacd1] 0b1010110011010001
Milliseconds:                    [0x70] 439 (deviation -2ms..2ms)
Seconds:                         [0x03] 3
Minute of day:                   [0x0160] 352 (05:51)
Day of year:                     [0x0dd] 221 (Day=9, Month=8)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-08-09 05:51:03'439 (deviation -2ms..2ms)