Interprete a UUID

Back

UUID: 
Your input:                      d50fe220-030d-8016-87e9-5ce32bd83b96

Various notations:

URN:                             urn:uuid:d50fe220-030d-8016-87e9-5ce32bd83b96
URI:                             uuid:d50fe220-030d-8016-87e9-5ce32bd83b96
Microsoft GUID syntax:           {D50FE220-030D-8016-87E9-5CE32BD83B96}
C++ struct syntax:               { 0xd50fe220, 0x030d, 0x8016, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.283208033915881505020564139673948535702
As OID (Microsoft):              1.2.840.113556.1.8000.2554.54543.57888.781.32790.34793.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15352738281847357462.9793460995456777110
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3574587936.51216406.2280217827.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.54543.57888.781.32790.34793.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd50fe220030d01607e95ce32bd83b96]
Custom data block1 (32 bit):     [0xd50fe220]
Custom data block2 (16 bit):     [0x030d]
Custom data block3 (12 bit):     [0x016]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b96]

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

Random 16 bits:                  [0xd50f] 0b1101010100001111
Milliseconds:                    [0xe2] 885 (deviation -2ms..2ms)
Seconds:                         [0x20] 32
Minute of day:                   [0x030d] 781 (13:00)
Day of year:                     [0x016] 22 (Day=22, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2025-01-22 13:00:32'885 (deviation -2ms..2ms)