Interpret a UUID
Back
Your input: 9d5a2c08-ab04-8514-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9d5a2c08-ab04-8514-87ea-5ce32bd83b97
URI: uuid:9d5a2c08-ab04-8514-87ea-5ce32bd83b97
Microsoft GUID syntax: {9D5A2C08-AB04-8514-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9d5a2c08, 0xab04, 0x8514, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.209156995168275188156278118437126421399
As OID (Microsoft): 1.2.840.113556.1.8000.2554.40282.11272.43780.34068.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11338423427599205652.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2639932424.2869200148.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.40282.11272.43780.34068.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9d5a2c08ab0451407ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9d5a2c08]
Custom data block2 (16 bit): [0xab04]
Custom data block3 (12 bit): [0x514]
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: [0x9d5a] 0b1001110101011010
Milliseconds: [0x2c] 172 (deviation -2ms..2ms)
Seconds: [0x08] 8
Minute of day: [0x04ab] 1195 (19:54)
Day of year: [0x145] 325 (Day=21, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-21 19:54:08'172 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing