Interpret a UUID
Back
Your input: 809de430-ef03-8114-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:809de430-ef03-8114-87ea-5ce32bd83b97
URI: uuid:809de430-ef03-8114-87ea-5ce32bd83b97
Microsoft GUID syntax: {809DE430-EF03-8114-87EA-5CE32BD83B97}
C++ struct syntax: { 0x809de430, 0xef03, 0x8114, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.170961002333571786623676685544578366359
As OID (Microsoft): 1.2.840.113556.1.8000.2554.32925.58416.61187.33044.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9267814507017896212.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2157831216.4009984276.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.32925.58416.61187.33044.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x809de430ef0311407ea5ce32bd83b97]
Custom data block1 (32 bit): [0x809de430]
Custom data block2 (16 bit): [0xef03]
Custom data block3 (12 bit): [0x114]
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: [0x809d] 0b1000000010011101
Milliseconds: [0xe4] 893 (deviation -2ms..2ms)
Seconds: [0x30] 48
Minute of day: [0x03ef] 1007 (16:46)
Day of year: [0x141] 321 (Day=17, 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-17 16:46:48'893 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing