Interpret a UUID
Back
Your input: 39b6f80d-1c04-8c0e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:39b6f80d-1c04-8c0e-87ea-5ce32bd83b97
URI: uuid:39b6f80d-1c04-8c0e-87ea-5ce32bd83b97
Microsoft GUID syntax: {39B6F80D-1C04-8C0E-87EA-5CE32BD83B97}
C++ struct syntax: { 0x39b6f80d, 0x1c04, 0x8c0e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.76716024864212439061242962095977806743
As OID (Microsoft): 1.2.840.113556.1.8000.2554.14774.63501.7172.35854.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4158784041111555086.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.968292365.470060046.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.14774.63501.7172.35854.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x39b6f80d1c04c0e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x39b6f80d]
Custom data block2 (16 bit): [0x1c04]
Custom data block3 (12 bit): [0xc0e]
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: [0x39b6] 0b0011100110110110
Milliseconds: [0xf8] 972 (deviation -2ms..2ms)
Seconds: [0x0d] 13
Minute of day: [0x041c] 1052 (17:31)
Day of year: [0x0ec] 236 (Day=24, 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-24 17:31:13'972 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing