Interprete a UUID
Back
Your input: 2f11810f-8c02-8713-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:2f11810f-8c02-8713-87e9-5ce32bd83b97
URI: uuid:2f11810f-8c02-8713-87e9-5ce32bd83b97
Microsoft GUID syntax: {2F11810F-8C02-8713-87E9-5CE32BD83B97}
C++ struct syntax: { 0x2f11810f, 0x8c02, 0x8713, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.62564602511078403981998028047208954775
As OID (Microsoft): 1.2.840.113556.1.8000.2554.12049.33039.35842.34579.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.3391633898160162579.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.789676303.2348975891.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.12049.33039.35842.34579.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x2f11810f8c0271307e95ce32bd83b97]
Custom data block1 (32 bit): [0x2f11810f]
Custom data block2 (16 bit): [0x8c02]
Custom data block3 (12 bit): [0x713]
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: [0x2f11] 0b0010111100010001
Milliseconds: [0x81] 505 (deviation -2ms..2ms)
Seconds: [0x0f] 15
Minute of day: [0x028c] 652 (10:51)
Day of year: [0x137] 311 (Day=7, 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-07 10:51:15'505 (deviation -2ms..2ms)