Interpret a UUID

Back

UUID: 
Your input:                      7eadd608-ff03-8905-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:7eadd608-ff03-8905-87ea-5ce32bd83b97
URI:                             uuid:7eadd608-ff03-8905-87ea-5ce32bd83b97
Microsoft GUID syntax:           {7EADD608-FF03-8905-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x7eadd608, 0xff03, 0x8905, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.168385335973829358085338343313124113303
As OID (Microsoft):              1.2.840.113556.1.8000.2554.32429.54792.65283.35077.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.9128187353876367621.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2125321736.4278421765.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.32429.54792.65283.35077.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x7eadd608ff0390507ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x7eadd608]
Custom data block2 (16 bit):     [0xff03]
Custom data block3 (12 bit):     [0x905]
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:                  [0x7ead] 0b0111111010101101
Milliseconds:                    [0xd6] 838 (deviation -2ms..2ms)
Seconds:                         [0x08] 8
Minute of day:                   [0x03ff] 1023 (17:02)
Day of year:                     [0x059] 89 (Day=30, 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-30 17:02:08'838 (deviation -2ms..2ms)