Interpret a UUID
Back
Your input: 794dc917-9001-8906-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:794dc917-9001-8906-87ea-5ce32bd83b97
URI: uuid:794dc917-9001-8906-87ea-5ce32bd83b97
Microsoft GUID syntax: {794DC917-9001-8906-87EA-5CE32BD83B97}
C++ struct syntax: { 0x794dc917, 0x9001, 0x8906, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.161240472979227771587368145139919240087
As OID (Microsoft): 1.2.840.113556.1.8000.2554.31053.51479.36865.35078.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8740863554833451270.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2035140887.2416019718.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.31053.51479.36865.35078.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x794dc917900190607ea5ce32bd83b97]
Custom data block1 (32 bit): [0x794dc917]
Custom data block2 (16 bit): [0x9001]
Custom data block3 (12 bit): [0x906]
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: [0x794d] 0b0111100101001101
Milliseconds: [0xc9] 787 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x0190] 400 (06:39)
Day of year: [0x069] 105 (Day=15, Month=4)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-04-15 06:39:23'787 (deviation -2ms..2ms)