Interpret a UUID

Back

Your input:                      ee44b413-0405-8a01-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ee44b413-0405-8a01-87ea-5ce32bd83b97
URI:                             uuid:ee44b413-0405-8a01-87ea-5ce32bd83b97
Microsoft GUID syntax:           {EE44B413-0405-8A01-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xee44b413, 0x0405, 0x8a01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.316712991523498727484743454855630699415
As OID (Microsoft):              1.2.840.113556.1.8000.2554.60996.46099.1029.35329.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.17169045673208023553.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3997479955.67471873.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.60996.46099.1029.35329.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xee44b4130405a0107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xee44b413]
Custom data block2 (16 bit):     [0x0405]
Custom data block3 (12 bit):     [0xa01]
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:                  [0xee44] 0b1110111001000100
Milliseconds:                    [0xb4] 705 (deviation -2ms..2ms)
Seconds:                         [0x13] 19
Minute of day:                   [0x0504] 1284 (21:23)
Day of year:                     [0x01a] 26 (Day=26, 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-26 21:23:19'705 (deviation -2ms..2ms)