Interpret a UUID
Back
Your input: bcadac05-6e04-8a0a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:bcadac05-6e04-8a0a-87ea-5ce32bd83b97
URI: uuid:bcadac05-6e04-8a0a-87ea-5ce32bd83b97
Microsoft GUID syntax: {BCADAC05-6E04-8A0A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xbcadac05, 0x6e04, 0x8a0a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.250796619568732188608748345387594038167
As OID (Microsoft): 1.2.840.113556.1.8000.2554.48301.44037.28164.35338.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13595711989422000650.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3165498373.1845791242.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.48301.44037.28164.35338.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xbcadac056e04a0a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xbcadac05]
Custom data block2 (16 bit): [0x6e04]
Custom data block3 (12 bit): [0xa0a]
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: [0xbcad] 0b1011110010101101
Milliseconds: [0xac] 674 (deviation -2ms..2ms)
Seconds: [0x05] 5
Minute of day: [0x046e] 1134 (18:53)
Day of year: [0x0aa] 170 (Day=19, 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-19 18:53:05'674 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing