Interpret a UUID
Back
Your input: d5f04a17-8604-8d0d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:d5f04a17-8604-8d0d-87ea-5ce32bd83b97
URI: uuid:d5f04a17-8604-8d0d-87ea-5ce32bd83b97
Microsoft GUID syntax: {D5F04A17-8604-8D0D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xd5f04a17, 0x8604, 0x8d0d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.284373217110270340733663557481284516759
As OID (Microsoft): 1.2.840.113556.1.8000.2554.54768.18967.34308.36109.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15415902989382356237.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3589294615.2248445197.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.54768.18967.34308.36109.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd5f04a178604d0d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xd5f04a17]
Custom data block2 (16 bit): [0x8604]
Custom data block3 (12 bit): [0xd0d]
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: [0xd5f0] 0b1101010111110000
Milliseconds: [0x4a] 290 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x0486] 1158 (19:17)
Day of year: [0x0dd] 221 (Day=9, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-09 19:17:23'290 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing