Interpret a UUID
Back
Your input: e386320f-6b03-8d13-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:e386320f-6b03-8d13-87ea-5ce32bd83b97
URI: uuid:e386320f-6b03-8d13-87ea-5ce32bd83b97
Microsoft GUID syntax: {E386320F-6B03-8D13-87EA-5CE32BD83B97}
C++ struct syntax: { 0xe386320f, 0x6b03, 0x8d13, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.302431538164241379391172281189443058583
As OID (Microsoft): 1.2.840.113556.1.8000.2554.58246.12815.27395.36115.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16394846535290162451.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3817222671.1795394835.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.58246.12815.27395.36115.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xe386320f6b03d1307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xe386320f]
Custom data block2 (16 bit): [0x6b03]
Custom data block3 (12 bit): [0xd13]
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: [0xe386] 0b1110001110000110
Milliseconds: [0x32] 196 (deviation -2ms..2ms)
Seconds: [0x0f] 15
Minute of day: [0x036b] 875 (14:34)
Day of year: [0x13d] 317 (Day=13, 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-13 14:34:15'196 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing