Interpret a UUID

Back

UUID: 
Your input:                      d086eb15-4a05-8607-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:d086eb15-4a05-8607-87ea-5ce32bd83b97
URI:                             uuid:d086eb15-4a05-8607-87ea-5ce32bd83b97
Microsoft GUID syntax:           {D086EB15-4A05-8607-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xd086eb15, 0x4a05, 0x8607, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.277179958955263007700222935865268648855
As OID (Microsoft):              1.2.840.113556.1.8000.2554.53382.60181.18949.34311.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15025955683436955143.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3498502933.1241875975.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.53382.60181.18949.34311.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd086eb154a0560707ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xd086eb15]
Custom data block2 (16 bit):     [0x4a05]
Custom data block3 (12 bit):     [0x607]
Custom data block4 (14 bit):     [0x07ea]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xd086] 0b1101000010000110
Milliseconds:                    [0xeb] 921 (deviation -2ms..2ms)
Seconds:                         [0x15] 21
Minute of day:                   [0x054a] 1354 (22:33)
Day of year:                     [0x076] 118 (Day=28, Month=4)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-04-28 22:33:21'921 (deviation -2ms..2ms)