Interpret a UUID
Back
Your input: d7950e34-ab00-850e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:d7950e34-ab00-850e-87ea-5ce32bd83b97
URI: uuid:d7950e34-ab00-850e-87ea-5ce32bd83b97
Microsoft GUID syntax: {D7950E34-AB00-850E-87EA-5CE32BD83B97}
C++ struct syntax: { 0xd7950e34, 0xab00, 0x850e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.286557959452200068878341439956249492375
As OID (Microsoft): 1.2.840.113556.1.8000.2554.55189.3636.43776.34062.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15534338109054420238.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3616869940.2868937998.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.55189.3636.43776.34062.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd7950e34ab0050e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xd7950e34]
Custom data block2 (16 bit): [0xab00]
Custom data block3 (12 bit): [0x50e]
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: [0xd795] 0b1101011110010101
Milliseconds: [0x0e] 55 (deviation -2ms..2ms)
Seconds: [0x34] 52
Minute of day: [0x00ab] 171 (02:50)
Day of year: [0x0e5] 229 (Day=17, 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-17 02:50:52'055 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing