Interpret a UUID
Back
Your input: ca0c1211-8c02-8a13-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:ca0c1211-8c02-8a13-87ea-5ce32bd83b97
URI: uuid:ca0c1211-8c02-8a13-87ea-5ce32bd83b97
Microsoft GUID syntax: {CA0C1211-8C02-8A13-87EA-5CE32BD83B97}
C++ struct syntax: { 0xca0c1211, 0x8c02, 0x8a13, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.268566729184438024004156817035123768215
As OID (Microsoft): 1.2.840.113556.1.8000.2554.51724.4625.35842.35347.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14559031561954691603.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3389788689.2348976659.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.51724.4625.35842.35347.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xca0c12118c02a1307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xca0c1211]
Custom data block2 (16 bit): [0x8c02]
Custom data block3 (12 bit): [0xa13]
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: [0xca0c] 0b1100101000001100
Milliseconds: [0x12] 71 (deviation -2ms..2ms)
Seconds: [0x11] 17
Minute of day: [0x028c] 652 (10:51)
Day of year: [0x13a] 314 (Day=10, 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-10 10:51:17'071 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing