Interpret a UUID
Back
Your input: e3029c00-7404-810d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:e3029c00-7404-810d-87ea-5ce32bd83b97
URI: uuid:e3029c00-7404-810d-87ea-5ce32bd83b97
Microsoft GUID syntax: {E3029C00-7404-810D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xe3029c00, 0x7404, 0x810d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.301748303728696848742439591549160930199
As OID (Microsoft): 1.2.840.113556.1.8000.2554.58114.39936.29700.33037.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16357808322323448077.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3808599040.1946452237.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.58114.39936.29700.33037.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xe3029c00740410d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xe3029c00]
Custom data block2 (16 bit): [0x7404]
Custom data block3 (12 bit): [0x10d]
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: [0xe302] 0b1110001100000010
Milliseconds: [0x9c] 611 (deviation -2ms..2ms)
Seconds: [0x00] 0
Minute of day: [0x0474] 1140 (18:59)
Day of year: [0x0d1] 209 (Day=28, 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-28 18:59:00'611 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing