Interpret a UUID
Back
Your input: d0769704-3202-8e11-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:d0769704-3202-8e11-87ea-5ce32bd83b97
URI: uuid:d0769704-3202-8e11-87ea-5ce32bd83b97
Microsoft GUID syntax: {D0769704-3202-8E11-87EA-5CE32BD83B97}
C++ struct syntax: { 0xd0769704, 0x3202, 0x8e11, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.277095177128809751925585275421984308119
As OID (Microsoft): 1.2.840.113556.1.8000.2554.53366.38660.12802.36369.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15021359651415559697.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3497432836.839028241.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.53366.38660.12802.36369.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd07697043202e1107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xd0769704]
Custom data block2 (16 bit): [0x3202]
Custom data block3 (12 bit): [0xe11]
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: [0xd076] 0b1101000001110110
Milliseconds: [0x97] 592 (deviation -2ms..2ms)
Seconds: [0x04] 4
Minute of day: [0x0232] 562 (09:21)
Day of year: [0x11e] 286 (Day=13, 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-13 09:21:04'592 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing