Interpret a UUID

Back

Your input:                      a2d06e2d-2d01-8003-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:a2d06e2d-2d01-8003-87ea-5ce32bd83b97
URI:                             uuid:a2d06e2d-2d01-8003-87ea-5ce32bd83b97
Microsoft GUID syntax:           {A2D06E2D-2D01-8003-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xa2d06e2d, 0x2d01, 0x8003, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.216417167707983969278616837636952177559
As OID (Microsoft):              1.2.840.113556.1.8000.2554.41680.28205.11521.32771.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.11731998169607798787.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2731568685.755073027.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.41680.28205.11521.32771.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xa2d06e2d2d0100307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xa2d06e2d]
Custom data block2 (16 bit):     [0x2d01]
Custom data block3 (12 bit):     [0x003]
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:                  [0xa2d0] 0b1010001011010000
Milliseconds:                    [0x6e] 431 (deviation -2ms..2ms)
Seconds:                         [0x2d] 45
Minute of day:                   [0x012d] 301 (05:00)
Day of year:                     [0x030] 48 (Day=17, Month=2)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-02-17 05:00:45'431 (deviation -2ms..2ms)