Interpret a UUID
Back
Your input: d9207f39-eb04-8801-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:d9207f39-eb04-8801-87ea-5ce32bd83b97
URI: uuid:d9207f39-eb04-8801-87ea-5ce32bd83b97
Microsoft GUID syntax: {D9207F39-EB04-8801-87EA-5CE32BD83B97}
C++ struct syntax: { 0xd9207f39, 0xeb04, 0x8801, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.288611209039559241260826898579202784151
As OID (Microsoft): 1.2.840.113556.1.8000.2554.55584.32569.60164.34817.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15645644992217909249.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3642785593.3942942721.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.55584.32569.60164.34817.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd9207f39eb0480107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xd9207f39]
Custom data block2 (16 bit): [0xeb04]
Custom data block3 (12 bit): [0x801]
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: [0xd920] 0b1101100100100000
Milliseconds: [0x7f] 498 (deviation -2ms..2ms)
Seconds: [0x39] 57
Minute of day: [0x04eb] 1259 (20:58)
Day of year: [0x018] 24 (Day=24, Month=1)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-01-24 20:58:57'498 (deviation -2ms..2ms)