Interpret a UUID
Back
Your input: 0fb2ef16-e403-8d0c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:0fb2ef16-e403-8d0c-87ea-5ce32bd83b97
URI: uuid:0fb2ef16-e403-8d0c-87ea-5ce32bd83b97
Microsoft GUID syntax: {0FB2EF16-E403-8D0C-87EA-5CE32BD83B97}
C++ struct syntax: { 0x0fb2ef16, 0xe403, 0x8d0c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.20867498087074660576036560233528048535
As OID (Microsoft): 1.2.840.113556.1.8000.2554.4018.61206.58371.36108.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.1131229338017172748.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.263384854.3825437964.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.4018.61206.58371.36108.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x0fb2ef16e403d0c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x0fb2ef16]
Custom data block2 (16 bit): [0xe403]
Custom data block3 (12 bit): [0xd0c]
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: [0x0fb2] 0b0000111110110010
Milliseconds: [0xef] 936 (deviation -2ms..2ms)
Seconds: [0x16] 22
Minute of day: [0x03e4] 996 (16:35)
Day of year: [0x0cd] 205 (Day=24, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-24 16:35:22'936 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing