Interprete a UUID

Back

UUID: 
Your input:                      8687050d-5003-8d13-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:8687050d-5003-8d13-87e9-5ce32bd83b97
URI:                             uuid:8687050d-5003-8d13-87e9-5ce32bd83b97
Microsoft GUID syntax:           {8687050D-5003-8D13-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x8687050d, 0x5003, 0x8d13, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.178817613977858153419872403935758662551
As OID (Microsoft):              1.2.840.113556.1.8000.2554.34439.1293.20483.36115.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.9693722277673405715.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2256995597.1342410003.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.34439.1293.20483.36115.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x8687050d5003d1307e95ce32bd83b97]
Custom data block1 (32 bit):     [0x8687050d]
Custom data block2 (16 bit):     [0x5003]
Custom data block3 (12 bit):     [0xd13]
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:                  [0x8687] 0b1000011010000111
Milliseconds:                    [0x05] 20 (deviation -2ms..2ms)
Seconds:                         [0x0d] 13
Minute of day:                   [0x0350] 848 (14:07)
Day of year:                     [0x13d] 317 (Day=13, Month=11)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-11-13 14:07:13'020 (deviation -2ms..2ms)