Interpret a UUID
Back
Your input: 0aabd106-d702-860e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:0aabd106-d702-860e-87ea-5ce32bd83b97
URI: uuid:0aabd106-d702-860e-87ea-5ce32bd83b97
Microsoft GUID syntax: {0AABD106-D702-860E-87EA-5CE32BD83B97}
C++ struct syntax: { 0x0aabd106, 0xd702, 0x860e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.14184402286177080566606699080885746583
As OID (Microsoft): 1.2.840.113556.1.8000.2554.2731.53510.55042.34318.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.768937988704077326.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.179032326.3607266830.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.2731.53510.55042.34318.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x0aabd106d70260e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x0aabd106]
Custom data block2 (16 bit): [0xd702]
Custom data block3 (12 bit): [0x60e]
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: [0x0aab] 0b0000101010101011
Milliseconds: [0xd1] 819 (deviation -2ms..2ms)
Seconds: [0x06] 6
Minute of day: [0x02d7] 727 (12:06)
Day of year: [0x0e6] 230 (Day=18, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-18 12:06:06'819 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing