Interprete a UUID

Back

UUID: 
Your input:                      85e0b738-0074-8058-87e8-5ce32bd83b96

Various notations:

URN:                             urn:uuid:85e0b738-0074-8058-87e8-5ce32bd83b96
URI:                             uuid:85e0b738-0074-8058-87e8-5ce32bd83b96
Microsoft GUID syntax:           {85E0B738-0074-8058-87E8-5CE32BD83B96}
C++ struct syntax:               { 0x85e0b738, 0x0074, 0x8058, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.177954114053581023030579420086251568022
As OID (Microsoft):              1.2.840.113556.1.8000.2554.34272.46904.116.32856.34792.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.9646911852981289048.9793179520480066454
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2246096696.7635032.2280152291.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.34272.46904.116.32856.34792.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x85e0b738007405807e85ce32bd83b96]
Custom data block1 (32 bit):     [0x85e0b738]
Custom data block2 (16 bit):     [0x0074]
Custom data block3 (12 bit):     [0x058]
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:                  [0x85e0] 0b1000010111100000
Milliseconds:                    [0xb7] 717 (deviation -2ms..2ms)
Seconds:                         [0x38] 56
Minute of day:                   [0x0074] 116 (01:55)
Day of year:                     [0x058] 88 (Day=28, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e8] 2024
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2024-03-28 01:55:56'717 (deviation -2ms..2ms)