Interprete a UUID
Back
Your input: f569c517-02cf-8146-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:f569c517-02cf-8146-87e8-5ce32bd83b96
URI: uuid:f569c517-02cf-8146-87e8-5ce32bd83b96
Microsoft GUID syntax: {F569C517-02CF-8146-87E8-5CE32BD83B96}
C++ struct syntax: { 0xf569c517, 0x02cf, 0x8146, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.326210047595260031120226187384261720982
As OID (Microsoft): 1.2.840.113556.1.8000.2554.62825.50455.719.33094.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17683882114469036358.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4117349655.47153478.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.62825.50455.719.33094.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf569c51702cf14607e85ce32bd83b96]
Custom data block1 (32 bit): [0xf569c517]
Custom data block2 (16 bit): [0x02cf]
Custom data block3 (12 bit): [0x146]
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: [0xf569] 0b1111010101101001
Milliseconds: [0xc5] 772 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x02cf] 719 (11:58)
Day of year: [0x146] 326 (Day=21, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7e8] 2024
Signature: [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time: 2024-11-21 11:58:23'772 (deviation -2ms..2ms)