Interpret a UUID
Back
Your input: 7cd8eb0d-6104-8806-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:7cd8eb0d-6104-8806-87ea-5ce32bd83b97
URI: uuid:7cd8eb0d-6104-8806-87ea-5ce32bd83b97
Microsoft GUID syntax: {7CD8EB0D-6104-8806-87EA-5CE32BD83B97}
C++ struct syntax: { 0x7cd8eb0d, 0x6104, 0x8806, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.165950575025021585854085486369440283543
As OID (Microsoft): 1.2.840.113556.1.8000.2554.31960.60173.24836.34822.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8996198698367354886.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2094590733.1627686918.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.31960.60173.24836.34822.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x7cd8eb0d610480607ea5ce32bd83b97]
Custom data block1 (32 bit): [0x7cd8eb0d]
Custom data block2 (16 bit): [0x6104]
Custom data block3 (12 bit): [0x806]
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: [0x7cd8] 0b0111110011011000
Milliseconds: [0xeb] 921 (deviation -2ms..2ms)
Seconds: [0x0d] 13
Minute of day: [0x0461] 1121 (18:40)
Day of year: [0x068] 104 (Day=14, Month=4)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-04-14 18:40:13'921 (deviation -2ms..2ms)