Interpret a UUID

Back

UUID: 
Your input:                      2ca1c403-7501-8d02-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:2ca1c403-7501-8d02-87ea-5ce32bd83b97
URI:                             uuid:2ca1c403-7501-8d02-87ea-5ce32bd83b97
Microsoft GUID syntax:           {2CA1C403-7501-8D02-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x2ca1c403, 0x7501, 0x8d02, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.59325967234938829901435329911025318807
As OID (Microsoft):              1.2.840.113556.1.8000.2554.11425.50179.29953.36098.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.3216067128046226690.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.748798979.1963035906.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.11425.50179.29953.36098.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x2ca1c4037501d0207ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x2ca1c403]
Custom data block2 (16 bit):     [0x7501]
Custom data block3 (12 bit):     [0xd02]
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:                  [0x2ca1] 0b0010110010100001
Milliseconds:                    [0xc4] 768 (deviation -2ms..2ms)
Seconds:                         [0x03] 3
Minute of day:                   [0x0175] 373 (06:12)
Day of year:                     [0x02d] 45 (Day=14, 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-14 06:12:03'768 (deviation -2ms..2ms)