Interpret a UUID
Back
Your input: c1be1431-4c00-8c06-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:c1be1431-4c00-8c06-87ea-5ce32bd83b97
URI: uuid:c1be1431-4c00-8c06-87ea-5ce32bd83b97
Microsoft GUID syntax: {C1BE1431-4C00-8C06-87EA-5CE32BD83B97}
C++ struct syntax: { 0xc1be1431, 0x4c00, 0x8c06, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.257527949143503938950420611851441683351
As OID (Microsoft): 1.2.840.113556.1.8000.2554.49598.5169.19456.35846.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13960618096856173574.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3250459697.1275104262.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.49598.5169.19456.35846.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xc1be14314c00c0607ea5ce32bd83b97]
Custom data block1 (32 bit): [0xc1be1431]
Custom data block2 (16 bit): [0x4c00]
Custom data block3 (12 bit): [0xc06]
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: [0xc1be] 0b1100000110111110
Milliseconds: [0x14] 78 (deviation -2ms..2ms)
Seconds: [0x31] 49
Minute of day: [0x004c] 76 (01:15)
Day of year: [0x06c] 108 (Day=18, 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-18 01:15:49'078 (deviation -2ms..2ms)