Interpret a UUID
Back
Your input: c85a8929-8e02-8804-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:c85a8929-8e02-8804-87ea-5ce32bd83b97
URI: uuid:c85a8929-8e02-8804-87ea-5ce32bd83b97
Microsoft GUID syntax: {C85A8929-8E02-8804-87EA-5CE32BD83B97}
C++ struct syntax: { 0xc85a8929, 0x8e02, 0x8804, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.266315687856671604002707696888715950999
As OID (Microsoft): 1.2.840.113556.1.8000.2554.51290.35113.36354.34820.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14437002367058741252.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3361376553.2382530564.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.51290.35113.36354.34820.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xc85a89298e0280407ea5ce32bd83b97]
Custom data block1 (32 bit): [0xc85a8929]
Custom data block2 (16 bit): [0x8e02]
Custom data block3 (12 bit): [0x804]
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: [0xc85a] 0b1100100001011010
Milliseconds: [0x89] 537 (deviation -2ms..2ms)
Seconds: [0x29] 41
Minute of day: [0x028e] 654 (10:53)
Day of year: [0x048] 72 (Day=13, Month=3)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-03-13 10:53:41'537 (deviation -2ms..2ms)