Interpret a UUID

Back

Your input:                      ae99ec38-ae04-8e01-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ae99ec38-ae04-8e01-87ea-5ce32bd83b97
URI:                             uuid:ae99ec38-ae04-8e01-87ea-5ce32bd83b97
Microsoft GUID syntax:           {AE99EC38-AE04-8E01-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xae99ec38, 0xae04, 0x8e01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.232084883825230651121924105725489462167
As OID (Microsoft):              1.2.840.113556.1.8000.2554.44697.60472.44548.36353.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12581346762218049025.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2929323064.2919534081.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.44697.60472.44548.36353.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xae99ec38ae04e0107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xae99ec38]
Custom data block2 (16 bit):     [0xae04]
Custom data block3 (12 bit):     [0xe01]
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:                  [0xae99] 0b1010111010011001
Milliseconds:                    [0xec] 925 (deviation -2ms..2ms)
Seconds:                         [0x38] 56
Minute of day:                   [0x04ae] 1198 (19:57)
Day of year:                     [0x01e] 30 (Day=30, 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-30 19:57:56'925 (deviation -2ms..2ms)