Interpret a UUID
Back
Your input: 0bcd660d-7504-8b0a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:0bcd660d-7504-8b0a-87ea-5ce32bd83b97
URI: uuid:0bcd660d-7504-8b0a-87ea-5ce32bd83b97
Microsoft GUID syntax: {0BCD660D-7504-8B0A-87EA-5CE32BD83B97}
C++ struct syntax: { 0x0bcd660d, 0x7504, 0x8b0a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.15687998681594637877188394391988353943
As OID (Microsoft): 1.2.840.113556.1.8000.2554.3021.26125.29956.35594.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.850448112626731786.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.198010381.1963232010.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.3021.26125.29956.35594.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x0bcd660d7504b0a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x0bcd660d]
Custom data block2 (16 bit): [0x7504]
Custom data block3 (12 bit): [0xb0a]
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: [0x0bcd] 0b0000101111001101
Milliseconds: [0x66] 400 (deviation -2ms..2ms)
Seconds: [0x0d] 13
Minute of day: [0x0475] 1141 (19:00)
Day of year: [0x0ab] 171 (Day=20, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-20 19:00:13'400 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing