Interpret a UUID
Back
Your input: 64e47433-d400-870e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:64e47433-d400-870e-87ea-5ce32bd83b97
URI: uuid:64e47433-d400-870e-87ea-5ce32bd83b97
Microsoft GUID syntax: {64E47433-D400-870E-87EA-5CE32BD83B97}
C++ struct syntax: { 0x64e47433, 0xd400, 0x870e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.134109000127999299680584555817111927703
As OID (Microsoft): 1.2.840.113556.1.8000.2554.25828.29747.54272.34574.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.7270063464431781646.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1692693555.3556804366.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.25828.29747.54272.34574.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x64e47433d40070e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x64e47433]
Custom data block2 (16 bit): [0xd400]
Custom data block3 (12 bit): [0x70e]
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: [0x64e4] 0b0110010011100100
Milliseconds: [0x74] 454 (deviation -2ms..2ms)
Seconds: [0x33] 51
Minute of day: [0x00d4] 212 (03:31)
Day of year: [0x0e7] 231 (Day=19, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-19 03:31:51'454 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing