Interpret a UUID
Back
Your input: e7e6f22d-cf01-8b11-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:e7e6f22d-cf01-8b11-87ea-5ce32bd83b97
URI: uuid:e7e6f22d-cf01-8b11-87ea-5ce32bd83b97
Microsoft GUID syntax: {E7E6F22D-CF01-8B11-87EA-5CE32BD83B97}
C++ struct syntax: { 0xe7e6f22d, 0xcf01, 0x8b11, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.308250807276235236532646786484154153879
As OID (Microsoft): 1.2.840.113556.1.8000.2554.59366.61997.52993.35601.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16710309745965239057.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3890672173.3472984849.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.59366.61997.52993.35601.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xe7e6f22dcf01b1107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xe7e6f22d]
Custom data block2 (16 bit): [0xcf01]
Custom data block3 (12 bit): [0xb11]
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: [0xe7e6] 0b1110011111100110
Milliseconds: [0xf2] 948 (deviation -2ms..2ms)
Seconds: [0x2d] 45
Minute of day: [0x01cf] 463 (07:42)
Day of year: [0x11b] 283 (Day=10, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-10-10 07:42:45'948 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing