Interpret a UUID

Back

Your input:                      5418e510-5004-8401-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:5418e510-5004-8401-87ea-5ce32bd83b97
URI:                             uuid:5418e510-5004-8401-87ea-5ce32bd83b97
Microsoft GUID syntax:           {5418E510-5004-8401-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x5418e510, 0x5004, 0x8401, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.111784412734751865517363299744690486167
As OID (Microsoft):              1.2.840.113556.1.8000.2554.21528.58640.20484.33793.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.6059845156851713025.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1410917648.1342473217.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.21528.58640.20484.33793.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x5418e510500440107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x5418e510]
Custom data block2 (16 bit):     [0x5004]
Custom data block3 (12 bit):     [0x401]
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:                  [0x5418] 0b0101010000011000
Milliseconds:                    [0xe5] 897 (deviation -2ms..2ms)
Seconds:                         [0x10] 16
Minute of day:                   [0x0450] 1104 (18:23)
Day of year:                     [0x014] 20 (Day=20, 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-20 18:23:16'897 (deviation -2ms..2ms)