Interpret a UUID
Back
Your input: 76f4e135-2d00-880b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:76f4e135-2d00-880b-87ea-5ce32bd83b97
URI: uuid:76f4e135-2d00-880b-87ea-5ce32bd83b97
Microsoft GUID syntax: {76F4E135-2D00-880B-87EA-5CE32BD83B97}
C++ struct syntax: { 0x76f4e135, 0x2d00, 0x880b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.158120391691283473722376080452381850519
As OID (Microsoft): 1.2.840.113556.1.8000.2554.30452.57653.11520.34827.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8571723609297422347.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1995759925.755009547.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.30452.57653.11520.34827.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x76f4e1352d0080b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x76f4e135]
Custom data block2 (16 bit): [0x2d00]
Custom data block3 (12 bit): [0x80b]
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: [0x76f4] 0b0111011011110100
Milliseconds: [0xe1] 881 (deviation -2ms..2ms)
Seconds: [0x35] 53
Minute of day: [0x002d] 45 (00:44)
Day of year: [0x0b8] 184 (Day=3, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-03 00:44:53'881 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing