Interpret a UUID

Back

UUID: 
Your input:                      aa48a42d-ce00-8801-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:aa48a42d-ce00-8801-87ea-5ce32bd83b97
URI:                             uuid:aa48a42d-ce00-8801-87ea-5ce32bd83b97
Microsoft GUID syntax:           {AA48A42D-CE00-8801-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xaa48a42d, 0xce00, 0x8801, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.226345934601447072292025356015248096151
As OID (Microsoft):              1.2.840.113556.1.8000.2554.43592.42029.52736.34817.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12270237701407541249.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2856887341.3456141313.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.43592.42029.52736.34817.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xaa48a42dce0080107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xaa48a42d]
Custom data block2 (16 bit):     [0xce00]
Custom data block3 (12 bit):     [0x801]
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:                  [0xaa48] 0b1010101001001000
Milliseconds:                    [0xa4] 642 (deviation -2ms..2ms)
Seconds:                         [0x2d] 45
Minute of day:                   [0x00ce] 206 (03:25)
Day of year:                     [0x018] 24 (Day=24, 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-24 03:25:45'642 (deviation -2ms..2ms)