Interpret a UUID
Back
Your input: db2adc17-d602-8813-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:db2adc17-d602-8813-87ea-5ce32bd83b97
URI: uuid:db2adc17-d602-8813-87ea-5ce32bd83b97
Microsoft GUID syntax: {DB2ADC17-D602-8813-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdb2adc17, 0xd602, 0x8813, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.291323471563548432677435684202133076887
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56106.56343.54786.34835.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15792677038260914195.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3677019159.3590490131.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56106.56343.54786.34835.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdb2adc17d60281307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdb2adc17]
Custom data block2 (16 bit): [0xd602]
Custom data block3 (12 bit): [0x813]
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: [0xdb2a] 0b1101101100101010
Milliseconds: [0xdc] 862 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x02d6] 726 (12:05)
Day of year: [0x138] 312 (Day=8, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-08 12:05:23'862 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing