Interpret a UUID

Back

UUID: 
Your input:                      bd6cd415-7701-8d01-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:bd6cd415-7701-8d01-87ea-5ce32bd83b97
URI:                             uuid:bd6cd415-7701-8d01-87ea-5ce32bd83b97
Microsoft GUID syntax:           {BD6CD415-7701-8D01-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xbd6cd415, 0x7701, 0x8d01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.251789160835528839292856043249778310039
As OID (Microsoft):              1.2.840.113556.1.8000.2554.48492.54293.30465.36097.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.13649517759309122817.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3178026005.1996590337.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.48492.54293.30465.36097.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xbd6cd4157701d0107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xbd6cd415]
Custom data block2 (16 bit):     [0x7701]
Custom data block3 (12 bit):     [0xd01]
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:                  [0xbd6c] 0b1011110101101100
Milliseconds:                    [0xd4] 831 (deviation -2ms..2ms)
Seconds:                         [0x15] 21
Minute of day:                   [0x0177] 375 (06:14)
Day of year:                     [0x01d] 29 (Day=29, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-29 06:14:21'831 (deviation -2ms..2ms)