Interprete a UUID

Back

UUID: 
Your input:                      5bc6e32e-aa02-8a14-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:5bc6e32e-aa02-8a14-87e9-5ce32bd83b97
URI:                             uuid:5bc6e32e-aa02-8a14-87e9-5ce32bd83b97
Microsoft GUID syntax:           {5BC6E32E-AA02-8A14-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x5bc6e32e, 0xaa02, 0x8a14, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.121992430198508266476612115510010067863
As OID (Microsoft):              1.2.840.113556.1.8000.2554.23494.58158.43522.35348.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.6613222892400445972.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1539760942.2852293140.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.23494.58158.43522.35348.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x5bc6e32eaa02a1407e95ce32bd83b97]
Custom data block1 (32 bit):     [0x5bc6e32e]
Custom data block2 (16 bit):     [0xaa02]
Custom data block3 (12 bit):     [0xa14]
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:                  [0x5bc6] 0b0101101111000110
Milliseconds:                    [0xe3] 889 (deviation -2ms..2ms)
Seconds:                         [0x2e] 46
Minute of day:                   [0x02aa] 682 (11:21)
Day of year:                     [0x14a] 330 (Day=26, 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-26 11:21:46'889 (deviation -2ms..2ms)