Interpret a UUID
Back
Your input: c6059933-6d04-890a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:c6059933-6d04-890a-87ea-5ce32bd83b97
URI: uuid:c6059933-6d04-890a-87ea-5ce32bd83b97
Microsoft GUID syntax: {C6059933-6D04-890A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xc6059933, 0x6d04, 0x890a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.263216211932751012838426938973965794199
As OID (Microsoft): 1.2.840.113556.1.8000.2554.50693.39219.27908.35082.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14268979440544680202.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3322255667.1829013770.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.50693.39219.27908.35082.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xc60599336d0490a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xc6059933]
Custom data block2 (16 bit): [0x6d04]
Custom data block3 (12 bit): [0x90a]
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: [0xc605] 0b1100011000000101
Milliseconds: [0x99] 599 (deviation -2ms..2ms)
Seconds: [0x33] 51
Minute of day: [0x046d] 1133 (18:52)
Day of year: [0x0a9] 169 (Day=18, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-18 18:52:51'599 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing