Interpret a UUID
Back
Your input: bf79da14-f000-8b03-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:bf79da14-f000-8b03-87ea-5ce32bd83b97
URI: uuid:bf79da14-f000-8b03-87ea-5ce32bd83b97
Microsoft GUID syntax: {BF79DA14-F000-8B03-87EA-5CE32BD83B97}
C++ struct syntax: { 0xbf79da14, 0xf000, 0x8b03, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.254515238338935551048316421007235103639
As OID (Microsoft): 1.2.840.113556.1.8000.2554.49017.55828.61440.35587.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13797298716886993667.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3212433940.4026567427.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.49017.55828.61440.35587.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xbf79da14f000b0307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xbf79da14]
Custom data block2 (16 bit): [0xf000]
Custom data block3 (12 bit): [0xb03]
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: [0xbf79] 0b1011111101111001
Milliseconds: [0xda] 854 (deviation -2ms..2ms)
Seconds: [0x14] 20
Minute of day: [0x00f0] 240 (03:59)
Day of year: [0x03b] 59 (Day=28, Month=2)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-02-28 03:59:20'854 (deviation -2ms..2ms)