Interpret a UUID
Back
Your input: ee09c139-3f00-8213-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:ee09c139-3f00-8213-87ea-5ce32bd83b97
URI: uuid:ee09c139-3f00-8213-87ea-5ce32bd83b97
Microsoft GUID syntax: {EE09C139-3F00-8213-87EA-5CE32BD83B97}
C++ struct syntax: { 0xee09c139, 0x3f00, 0x8213, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.316406912709093729171891311719642315671
As OID (Microsoft): 1.2.840.113556.1.8000.2554.60937.49465.16128.33299.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17152453107431539219.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3993616697.1056997907.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.60937.49465.16128.33299.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xee09c1393f0021307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xee09c139]
Custom data block2 (16 bit): [0x3f00]
Custom data block3 (12 bit): [0x213]
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: [0xee09] 0b1110111000001001
Milliseconds: [0xc1] 756 (deviation -2ms..2ms)
Seconds: [0x39] 57
Minute of day: [0x003f] 63 (01:02)
Day of year: [0x132] 306 (Day=2, 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-02 01:02:57'756 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing