Interpret a UUID
Back
Your input: 9a806322-ff02-8301-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9a806322-ff02-8301-87ea-5ce32bd83b97
URI: uuid:9a806322-ff02-8301-87ea-5ce32bd83b97
Microsoft GUID syntax: {9A806322-FF02-8301-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9a806322, 0xff02, 0x8301, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.205367736079999503378329604022519479191
As OID (Microsoft): 1.2.840.113556.1.8000.2554.39552.25378.65282.33537.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11133007280818258689.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2592105250.4278354689.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.39552.25378.65282.33537.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9a806322ff0230107ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9a806322]
Custom data block2 (16 bit): [0xff02]
Custom data block3 (12 bit): [0x301]
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: [0x9a80] 0b1001101010000000
Milliseconds: [0x63] 388 (deviation -2ms..2ms)
Seconds: [0x22] 34
Minute of day: [0x02ff] 767 (12:46)
Day of year: [0x013] 19 (Day=19, Month=1)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-01-19 12:46:34'388 (deviation -2ms..2ms)