Interpret a UUID

Back

Your input:                      2b2d2225-ce04-8f03-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:2b2d2225-ce04-8f03-87ea-5ce32bd83b97
URI:                             uuid:2b2d2225-ce04-8f03-87ea-5ce32bd83b97
Microsoft GUID syntax:           {2B2D2225-CE04-8F03-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x2b2d2225, 0xce04, 0x8f03, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.57391149774513410052739048819371031447
As OID (Microsoft):              1.2.840.113556.1.8000.2554.11053.8741.52740.36611.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.3111180463348420355.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.724378149.3456405251.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.11053.8741.52740.36611.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x2b2d2225ce04f0307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x2b2d2225]
Custom data block2 (16 bit):     [0xce04]
Custom data block3 (12 bit):     [0xf03]
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:                  [0x2b2d] 0b0010101100101101
Milliseconds:                    [0x22] 133 (deviation -2ms..2ms)
Seconds:                         [0x25] 37
Minute of day:                   [0x04ce] 1230 (20:29)
Day of year:                     [0x03f] 63 (Day=4, 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-04 20:29:37'133 (deviation -2ms..2ms)