Interprete a UUID

Back

UUID: 
Your input:                      0eca4d38-4d02-8415-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:0eca4d38-4d02-8415-87e9-5ce32bd83b97
URI:                             uuid:0eca4d38-4d02-8415-87e9-5ce32bd83b97
Microsoft GUID syntax:           {0ECA4D38-4D02-8415-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x0eca4d38, 0x4d02, 0x8415, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.19659602112562826736475633165920648087
As OID (Microsoft):              1.2.840.113556.1.8000.2554.3786.19768.19714.33813.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.1065749166032061461.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.248139064.1292010517.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.3786.19768.19714.33813.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x0eca4d384d0241507e95ce32bd83b97]
Custom data block1 (32 bit):     [0x0eca4d38]
Custom data block2 (16 bit):     [0x4d02]
Custom data block3 (12 bit):     [0x415]
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:                  [0x0eca] 0b0000111011001010
Milliseconds:                    [0x4d] 302 (deviation -2ms..2ms)
Seconds:                         [0x38] 56
Minute of day:                   [0x024d] 589 (09:48)
Day of year:                     [0x154] 340 (Day=6, Month=12)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-12-06 09:48:56'302 (deviation -2ms..2ms)