Interpret a UUID

Back

Your input:                      f26e0605-9400-8301-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:f26e0605-9400-8301-87ea-5ce32bd83b97
URI:                             uuid:f26e0605-9400-8301-87ea-5ce32bd83b97
Microsoft GUID syntax:           {F26E0605-9400-8301-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xf26e0605, 0x9400, 0x8301, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.322244449770791306875012707474218695575
As OID (Microsoft):              1.2.840.113556.1.8000.2554.62062.1541.37888.33537.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.17468906625644397313.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4067296773.2483061505.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.62062.1541.37888.33537.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xf26e0605940030107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xf26e0605]
Custom data block2 (16 bit):     [0x9400]
Custom data block3 (12 bit):     [0x301]
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:                  [0xf26e] 0b1111001001101110
Milliseconds:                    [0x06] 24 (deviation -2ms..2ms)
Seconds:                         [0x05] 5
Minute of day:                   [0x0094] 148 (02:27)
Day of year:                     [0x013] 19 (Day=19, 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-19 02:27:05'024 (deviation -2ms..2ms)