Interpret a UUID
Back
Your input: 5ced6c02-d304-8614-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:5ced6c02-d304-8614-87ea-5ce32bd83b97
URI: uuid:5ced6c02-d304-8614-87ea-5ce32bd83b97
Microsoft GUID syntax: {5CED6C02-D304-8614-87EA-5CE32BD83B97}
C++ struct syntax: { 0x5ced6c02, 0xd304, 0x8614, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.123521740691685339815466035160754437015
As OID (Microsoft): 1.2.840.113556.1.8000.2554.23789.27650.54020.34324.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.6696126980355819028.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1559063554.3540289044.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.23789.27650.54020.34324.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x5ced6c02d30461407ea5ce32bd83b97]
Custom data block1 (32 bit): [0x5ced6c02]
Custom data block2 (16 bit): [0xd304]
Custom data block3 (12 bit): [0x614]
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: [0x5ced] 0b0101110011101101
Milliseconds: [0x6c] 423 (deviation -2ms..2ms)
Seconds: [0x02] 2
Minute of day: [0x04d3] 1235 (20:34)
Day of year: [0x146] 326 (Day=22, 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-22 20:34:02'423 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing