Interpret a UUID

Back

Your input:                      05f5e52e-1705-8004-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:05f5e52e-1705-8004-87ea-5ce32bd83b97
URI:                             uuid:05f5e52e-1705-8004-87ea-5ce32bd83b97
Microsoft GUID syntax:           {05F5E52E-1705-8004-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x05f5e52e, 0x1705, 0x8004, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.7922901032685128423675155932029402007
As OID (Microsoft):              1.2.840.113556.1.8000.2554.1525.58670.5893.32772.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.429501325601243140.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.100001070.386236420.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.1525.58670.5893.32772.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x05f5e52e170500407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x05f5e52e]
Custom data block2 (16 bit):     [0x1705]
Custom data block3 (12 bit):     [0x004]
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:                  [0x05f5] 0b0000010111110101
Milliseconds:                    [0xe5] 897 (deviation -2ms..2ms)
Seconds:                         [0x2e] 46
Minute of day:                   [0x0517] 1303 (21:42)
Day of year:                     [0x040] 64 (Day=5, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-05 21:42:46'897 (deviation -2ms..2ms)