Interprete a UUID

Back

UUID: 
Your input:                      66ee0e2a-0303-800d-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:66ee0e2a-0303-800d-87e9-5ce32bd83b97
URI:                             uuid:66ee0e2a-0303-800d-87e9-5ce32bd83b97
Microsoft GUID syntax:           {66EE0E2A-0303-800D-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x66ee0e2a, 0x0303, 0x800d, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.136817309504642671253700512827280210839
As OID (Microsoft):              1.2.840.113556.1.8000.2554.26350.3626.771.32781.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.7416881209927761933.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1726877226.50561037.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.26350.3626.771.32781.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x66ee0e2a030300d07e95ce32bd83b97]
Custom data block1 (32 bit):     [0x66ee0e2a]
Custom data block2 (16 bit):     [0x0303]
Custom data block3 (12 bit):     [0x00d]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3

Random 16 bits:                  [0x66ee] 0b0110011011101110
Milliseconds:                    [0x0e] 55 (deviation -2ms..2ms)
Seconds:                         [0x2a] 42
Minute of day:                   [0x0303] 771 (12:50)
Day of year:                     [0x0d0] 208 (Day=27, Month=7)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-07-27 12:50:42'055 (deviation -2ms..2ms)