Interpret a UUID
Back
Your input: ab02dd2c-9b03-860a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:ab02dd2c-9b03-860a-87ea-5ce32bd83b97
URI: uuid:ab02dd2c-9b03-860a-87ea-5ce32bd83b97
Microsoft GUID syntax: {AB02DD2C-9B03-860A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xab02dd2c, 0x9b03, 0x860a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.227312857819473677859739832038918208407
As OID (Microsoft): 1.2.840.113556.1.8000.2554.43778.56620.39683.34314.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12322654714088097290.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2869091628.2600699402.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.43778.56620.39683.34314.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xab02dd2c9b0360a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xab02dd2c]
Custom data block2 (16 bit): [0x9b03]
Custom data block3 (12 bit): [0x60a]
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: [0xab02] 0b1010101100000010
Milliseconds: [0xdd] 866 (deviation -2ms..2ms)
Seconds: [0x2c] 44
Minute of day: [0x039b] 923 (15:22)
Day of year: [0x0a6] 166 (Day=15, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-15 15:22:44'866 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing