Interpret a UUID
Back
Your input: e5c57113-0b05-8109-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:e5c57113-0b05-8109-87ea-5ce32bd83b97
URI: uuid:e5c57113-0b05-8109-87ea-5ce32bd83b97
Microsoft GUID syntax: {E5C57113-0B05-8109-87EA-5CE32BD83B97}
C++ struct syntax: { 0xe5c57113, 0x0b05, 0x8109, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.305418386936908385445796243117683784599
As OID (Microsoft): 1.2.840.113556.1.8000.2554.58821.28947.2821.33033.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16556763931700723977.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3854922003.184910089.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.58821.28947.2821.33033.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xe5c571130b0510907ea5ce32bd83b97]
Custom data block1 (32 bit): [0xe5c57113]
Custom data block2 (16 bit): [0x0b05]
Custom data block3 (12 bit): [0x109]
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: [0xe5c5] 0b1110010111000101
Milliseconds: [0x71] 443 (deviation -2ms..2ms)
Seconds: [0x13] 19
Minute of day: [0x050b] 1291 (21:30)
Day of year: [0x091] 145 (Day=25, Month=5)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-05-25 21:30:19'443 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing