Interpret a UUID

Back

Your input:                      26ab4935-a701-8503-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:26ab4935-a701-8503-87ea-5ce32bd83b97
URI:                             uuid:26ab4935-a701-8503-87ea-5ce32bd83b97
Microsoft GUID syntax:           {26AB4935-A701-8503-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x26ab4935, 0xa701, 0x8503, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.51400031469315772228634661230711683991
As OID (Microsoft):              1.2.840.113556.1.8000.2554.9899.18741.42753.34051.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.2786401289242772739.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.648759605.2801894659.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.9899.18741.42753.34051.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x26ab4935a70150307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x26ab4935]
Custom data block2 (16 bit):     [0xa701]
Custom data block3 (12 bit):     [0x503]
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:                  [0x26ab] 0b0010011010101011
Milliseconds:                    [0x49] 286 (deviation -2ms..2ms)
Seconds:                         [0x35] 53
Minute of day:                   [0x01a7] 423 (07:02)
Day of year:                     [0x035] 53 (Day=22, 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-22 07:02:53'286 (deviation -2ms..2ms)