Interprete a UUID

Back

UUID: 
Your input:                      af9ec717-02cf-8146-87e8-5ce32bd83b96

Various notations:

URN:                             urn:uuid:af9ec717-02cf-8146-87e8-5ce32bd83b96
URI:                             uuid:af9ec717-02cf-8146-87e8-5ce32bd83b96
Microsoft GUID syntax:           {AF9EC717-02CF-8146-87E8-5CE32BD83B96}
C++ struct syntax:               { 0xaf9ec717, 0x02cf, 0x8146, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.233439320188637473184612657364588837782
As OID (Microsoft):              1.2.840.113556.1.8000.2554.44958.50967.719.33094.34792.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12654770904603001158.9793179520480066454
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2946418455.47153478.2280152291.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.44958.50967.719.33094.34792.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xaf9ec71702cf14607e85ce32bd83b96]
Custom data block1 (32 bit):     [0xaf9ec717]
Custom data block2 (16 bit):     [0x02cf]
Custom data block3 (12 bit):     [0x146]
Custom data block4 (14 bit):     [0x07e8]
Custom data block5 (48 bit):     [0x5ce32bd83b96]

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

Random 16 bits:                  [0xaf9e] 0b1010111110011110
Milliseconds:                    [0xc7] 780 (deviation -2ms..2ms)
Seconds:                         [0x17] 23
Minute of day:                   [0x02cf] 719 (11:58)
Day of year:                     [0x146] 326 (Day=21, Month=11)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e8] 2024
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2024-11-21 11:58:23'780 (deviation -2ms..2ms)