Interpret a UUID
Back
Your input: e3ffc42a-a902-880c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:e3ffc42a-a902-880c-87ea-5ce32bd83b97
URI: uuid:e3ffc42a-a902-880c-87ea-5ce32bd83b97
Microsoft GUID syntax: {E3FFC42A-A902-880C-87EA-5CE32BD83B97}
C++ struct syntax: { 0xe3ffc42a, 0xa902, 0x880c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.303062769474273452505387639337221897111
As OID (Microsoft): 1.2.840.113556.1.8000.2554.58367.50218.43266.34828.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16429065653174044684.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3825189930.2835515404.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.58367.50218.43266.34828.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xe3ffc42aa90280c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xe3ffc42a]
Custom data block2 (16 bit): [0xa902]
Custom data block3 (12 bit): [0x80c]
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: [0xe3ff] 0b1110001111111111
Milliseconds: [0xc4] 768 (deviation -2ms..2ms)
Seconds: [0x2a] 42
Minute of day: [0x02a9] 681 (11:20)
Day of year: [0x0c8] 200 (Day=19, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-19 11:20:42'768 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing