Interpret a UUID
Back
Your input: eca40b39-9605-890d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:eca40b39-9605-890d-87ea-5ce32bd83b97
URI: uuid:eca40b39-9605-890d-87ea-5ce32bd83b97
Microsoft GUID syntax: {ECA40B39-9605-890D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xeca40b39, 0x9605, 0x890d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.314549571358980204533928775900565355415
As OID (Microsoft): 1.2.840.113556.1.8000.2554.60580.2873.38405.35085.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17051766431089527053.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3970173753.2516945165.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.60580.2873.38405.35085.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xeca40b39960590d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xeca40b39]
Custom data block2 (16 bit): [0x9605]
Custom data block3 (12 bit): [0x90d]
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: [0xeca4] 0b1110110010100100
Milliseconds: [0x0b] 43 (deviation -2ms..2ms)
Seconds: [0x39] 57
Minute of day: [0x0596] 1430 (23:49)
Day of year: [0x0d9] 217 (Day=5, 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-05 23:49:57'043 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing