Interpret a UUID
Back
Your input: d2c82105-7301-810d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:d2c82105-7301-810d-87ea-5ce32bd83b97
URI: uuid:d2c82105-7301-810d-87ea-5ce32bd83b97
Microsoft GUID syntax: {D2C82105-7301-810D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xd2c82105, 0x7301, 0x810d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.280177008237789626402103263297143323543
As OID (Microsoft): 1.2.840.113556.1.8000.2554.53960.8453.29441.33037.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15188426050595029261.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3536331013.1929478413.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.53960.8453.29441.33037.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd2c82105730110d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xd2c82105]
Custom data block2 (16 bit): [0x7301]
Custom data block3 (12 bit): [0x10d]
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: [0xd2c8] 0b1101001011001000
Milliseconds: [0x21] 129 (deviation -2ms..2ms)
Seconds: [0x05] 5
Minute of day: [0x0173] 371 (06:10)
Day of year: [0x0d1] 209 (Day=28, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-28 06:10:05'129 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing