Interprete a UUID

Back

UUID: 
Your input:                      370a6219-030f-806f-87e8-5ce32bd83b96

Various notations:

URN:                             urn:uuid:370a6219-030f-806f-87e8-5ce32bd83b96
URI:                             uuid:370a6219-030f-806f-87e8-5ce32bd83b96
Microsoft GUID syntax:           {370A6219-030F-806F-87E8-5CE32BD83B96}
C++ struct syntax:               { 0x370a6219, 0x030f, 0x806f, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.73161452394548137443354513608558525334
As OID (Microsoft):              1.2.840.113556.1.8000.2554.14090.25113.783.32879.34792.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.3966090281418195055.9793179520480066454
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.923427353.51347567.2280152291.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.14090.25113.783.32879.34792.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x370a6219030f06f07e85ce32bd83b96]
Custom data block1 (32 bit):     [0x370a6219]
Custom data block2 (16 bit):     [0x030f]
Custom data block3 (12 bit):     [0x06f]
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:                  [0x370a] 0b0011011100001010
Milliseconds:                    [0x62] 384 (deviation -2ms..2ms)
Seconds:                         [0x19] 25
Minute of day:                   [0x030f] 783 (13:02)
Day of year:                     [0x06f] 111 (Day=20, Month=4)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e8] 2024
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2024-04-20 13:02:25'384 (deviation -2ms..2ms)