Interprete a UUID
Back
Your input: 796bfd03-2704-8b14-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:796bfd03-2704-8b14-87e9-5ce32bd83b97
URI: uuid:796bfd03-2704-8b14-87e9-5ce32bd83b97
Microsoft GUID syntax: {796BFD03-2704-8B14-87E9-5CE32BD83B97}
C++ struct syntax: { 0x796bfd03, 0x2704, 0x8b14, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.161397294953227666467004066383653256087
As OID (Microsoft): 1.2.840.113556.1.8000.2554.31083.64771.9988.35604.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8749364891078658836.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2037120259.654609172.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.31083.64771.9988.35604.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x796bfd032704b1407e95ce32bd83b97]
Custom data block1 (32 bit): [0x796bfd03]
Custom data block2 (16 bit): [0x2704]
Custom data block3 (12 bit): [0xb14]
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: [0x796b] 0b0111100101101011
Milliseconds: [0xfd] 991 (deviation -2ms..2ms)
Seconds: [0x03] 3
Minute of day: [0x0427] 1063 (17:42)
Day of year: [0x14b] 331 (Day=27, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-11-27 17:42:03'991 (deviation -2ms..2ms)