Interpret a UUID
Back
Your input: 7c2f5f0c-5c00-8a07-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:7c2f5f0c-5c00-8a07-87ea-5ce32bd83b97
URI: uuid:7c2f5f0c-5c00-8a07-87ea-5ce32bd83b97
Microsoft GUID syntax: {7C2F5F0C-5C00-8A07-87EA-5CE32BD83B97}
C++ struct syntax: { 0x7c2f5f0c, 0x5c00, 0x8a07, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.165070237237804274947534668233755343767
As OID (Microsoft): 1.2.840.113556.1.8000.2554.31791.24332.23552.35335.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8948475491296250375.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2083479308.1543539207.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.31791.24332.23552.35335.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x7c2f5f0c5c00a0707ea5ce32bd83b97]
Custom data block1 (32 bit): [0x7c2f5f0c]
Custom data block2 (16 bit): [0x5c00]
Custom data block3 (12 bit): [0xa07]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x7c2f] 0b0111110000101111
Milliseconds: [0x5f] 372 (deviation -2ms..2ms)
Seconds: [0x0c] 12
Minute of day: [0x005c] 92 (01:31)
Day of year: [0x07a] 122 (Day=2, Month=5)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-05-02 01:31:12'372 (deviation -2ms..2ms)