Interprete a UUID
Back
Your input: 1e41f42f-020d-80d1-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:1e41f42f-020d-80d1-87e8-5ce32bd83b96
URI: uuid:1e41f42f-020d-80d1-87e8-5ce32bd83b96
Microsoft GUID syntax: {1E41F42F-020D-80D1-87E8-5CE32BD83B96}
C++ struct syntax: { 0x1e41f42f, 0x020d, 0x80d1, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.40219291801654463544346182652773546902
As OID (Microsoft): 1.2.840.113556.1.8000.2554.7745.62511.525.32977.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.2180292177359110353.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.507638831.34439377.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.7745.62511.525.32977.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x1e41f42f020d0d107e85ce32bd83b96]
Custom data block1 (32 bit): [0x1e41f42f]
Custom data block2 (16 bit): [0x020d]
Custom data block3 (12 bit): [0x0d1]
Custom data block4 (14 bit): [0x07e8]
Custom data block5 (48 bit): [0x5ce32bd83b96]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 2
Random 16 bits: [0x1e41] 0b0001111001000001
Milliseconds: [0xf4] 956 (deviation -2ms..2ms)
Seconds: [0x2f] 47
Minute of day: [0x020d] 525 (08:44)
Day of year: [0x0d1] 209 (Day=27, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7e8] 2024
Signature: [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time: 2024-07-27 08:44:47'956 (deviation -2ms..2ms)