Interprete a UUID
Back
Your input: 357a4f31-b202-8d14-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:357a4f31-b202-8d14-87e9-5ce32bd83b97
URI: uuid:357a4f31-b202-8d14-87e9-5ce32bd83b97
Microsoft GUID syntax: {357A4F31-B202-8D14-87E9-5CE32BD83B97}
C++ struct syntax: { 0x357a4f31, 0xb202, 0x8d14, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.71084150240971857747739607244511656855
As OID (Microsoft): 1.2.840.113556.1.8000.2554.13690.20273.45570.36116.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.3853479506027384084.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.897208113.2986511636.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.13690.20273.45570.36116.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x357a4f31b202d1407e95ce32bd83b97]
Custom data block1 (32 bit): [0x357a4f31]
Custom data block2 (16 bit): [0xb202]
Custom data block3 (12 bit): [0xd14]
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: [0x357a] 0b0011010101111010
Milliseconds: [0x4f] 309 (deviation -2ms..2ms)
Seconds: [0x31] 49
Minute of day: [0x02b2] 690 (11:29)
Day of year: [0x14d] 333 (Day=29, 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-29 11:29:49'309 (deviation -2ms..2ms)