Interpret a UUID
Back
Your input: d9830d32-e704-8916-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:d9830d32-e704-8916-87e9-5ce32bd83b97
URI: uuid:d9830d32-e704-8916-87e9-5ce32bd83b97
Microsoft GUID syntax: {D9830D32-E704-8916-87E9-5CE32BD83B97}
C++ struct syntax: { 0xd9830d32, 0xe704, 0x8916, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.289122933678024300376235171242011278231
As OID (Microsoft): 1.2.840.113556.1.8000.2554.55683.3378.59140.35094.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15673385640454818070.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3649244466.3875834134.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.55683.3378.59140.35094.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xd9830d32e70491607e95ce32bd83b97]
Custom data block1 (32 bit): [0xd9830d32]
Custom data block2 (16 bit): [0xe704]
Custom data block3 (12 bit): [0x916]
Custom data block4 (14 bit): [0x07e9]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0xd983] 0b1101100110000011
Milliseconds: [0x0d] 51 (deviation -2ms..2ms)
Seconds: [0x32] 50
Minute of day: [0x04e7] 1255 (20:54)
Day of year: [0x169] 361 (Day=27, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-12-27 20:54:50'051 (deviation -2ms..2ms)