Interprete a UUID
Back
Your input: 0b7b7209-02e2-8164-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:0b7b7209-02e2-8164-87e8-5ce32bd83b96
URI: uuid:0b7b7209-02e2-8164-87e8-5ce32bd83b96
Microsoft GUID syntax: {0B7B7209-02E2-8164-87E8-5CE32BD83B96}
C++ struct syntax: { 0x0b7b7209, 0x02e2, 0x8164, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.15262473375874935613677970446720973718
As OID (Microsoft): 1.2.840.113556.1.8000.2554.2939.29193.738.33124.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.827380339581288804.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.192639497.48398692.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.2939.29193.738.33124.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x0b7b720902e216407e85ce32bd83b96]
Custom data block1 (32 bit): [0x0b7b7209]
Custom data block2 (16 bit): [0x02e2]
Custom data block3 (12 bit): [0x164]
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: [0x0b7b] 0b0000101101111011
Milliseconds: [0x72] 447 (deviation -2ms..2ms)
Seconds: [0x09] 9
Minute of day: [0x02e2] 738 (12:17)
Day of year: [0x164] 356 (Day=21, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e8] 2024
Signature: [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time: 2024-12-21 12:17:09'447 (deviation -2ms..2ms)