Interpret a UUID
Back
Your input: 03339900-7a04-870f-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:03339900-7a04-870f-87ea-5ce32bd83b97
URI: uuid:03339900-7a04-870f-87ea-5ce32bd83b97
Microsoft GUID syntax: {03339900-7A04-870F-87EA-5CE32BD83B97}
C++ struct syntax: { 0x03339900, 0x7a04, 0x870f, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.4255594373572027240793988302380743575
As OID (Microsoft): 1.2.840.113556.1.8000.2554.819.39168.31236.34575.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.230696233252194063.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.53713152.2047117071.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.819.39168.31236.34575.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x033399007a0470f07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x03339900]
Custom data block2 (16 bit): [0x7a04]
Custom data block3 (12 bit): [0x70f]
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: [0x0333] 0b0000001100110011
Milliseconds: [0x99] 599 (deviation -2ms..2ms)
Seconds: [0x00] 0
Minute of day: [0x047a] 1146 (19:05)
Day of year: [0x0f7] 247 (Day=4, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-04 19:05:00'599 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing