Interprete a UUID

Back

UUID: 
Your input:                      a1217d1a-9a02-8e13-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:a1217d1a-9a02-8e13-87e9-5ce32bd83b97
URI:                             uuid:a1217d1a-9a02-8e13-87e9-5ce32bd83b97
Microsoft GUID syntax:           {A1217D1A-9A02-8E13-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xa1217d1a, 0x9a02, 0x8e13, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.214179590526499566979378749650077498263
As OID (Microsoft):              1.2.840.113556.1.8000.2554.41249.32026.39426.36371.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.11610698867544329747.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2703326490.2583858707.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.41249.32026.39426.36371.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xa1217d1a9a02e1307e95ce32bd83b97]
Custom data block1 (32 bit):     [0xa1217d1a]
Custom data block2 (16 bit):     [0x9a02]
Custom data block3 (12 bit):     [0xe13]
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:                  [0xa121] 0b1010000100100001
Milliseconds:                    [0x7d] 490 (deviation -2ms..2ms)
Seconds:                         [0x1a] 26
Minute of day:                   [0x029a] 666 (11:05)
Day of year:                     [0x13e] 318 (Day=14, 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-14 11:05:26'490 (deviation -2ms..2ms)