Interpret a UUID
Back
Your input: ec3f1112-d000-8613-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:ec3f1112-d000-8613-87ea-5ce32bd83b97
URI: uuid:ec3f1112-d000-8613-87ea-5ce32bd83b97
Microsoft GUID syntax: {EC3F1112-D000-8613-87EA-5CE32BD83B97}
C++ struct syntax: { 0xec3f1112, 0xd000, 0x8613, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.314025267998771542681281529980093217687
As OID (Microsoft): 1.2.840.113556.1.8000.2554.60479.4370.53248.34323.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17023343888980542995.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3963556114.3489695251.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.60479.4370.53248.34323.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xec3f1112d00061307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xec3f1112]
Custom data block2 (16 bit): [0xd000]
Custom data block3 (12 bit): [0x613]
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: [0xec3f] 0b1110110000111111
Milliseconds: [0x11] 67 (deviation -2ms..2ms)
Seconds: [0x12] 18
Minute of day: [0x00d0] 208 (03:27)
Day of year: [0x136] 310 (Day=6, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-06 03:27:18'067 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing