Interpret a UUID
Back
Your input: df25cc1c-c602-8411-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:df25cc1c-c602-8411-87ea-5ce32bd83b97
URI: uuid:df25cc1c-c602-8411-87ea-5ce32bd83b97
Microsoft GUID syntax: {DF25CC1C-C602-8411-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdf25cc1c, 0xc602, 0x8411, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.296614097935030797092002224047711075223
As OID (Microsoft): 1.2.840.113556.1.8000.2554.57125.52252.50690.33809.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16079482468549428241.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3743796252.3322053649.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.57125.52252.50690.33809.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdf25cc1cc60241107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdf25cc1c]
Custom data block2 (16 bit): [0xc602]
Custom data block3 (12 bit): [0x411]
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: [0xdf25] 0b1101111100100101
Milliseconds: [0xcc] 799 (deviation -2ms..2ms)
Seconds: [0x1c] 28
Minute of day: [0x02c6] 710 (11:49)
Day of year: [0x114] 276 (Day=3, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-10-03 11:49:28'799 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing