Interpret a UUID
Back
Your input: 84e5e639-5c02-850c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:84e5e639-5c02-850c-87ea-5ce32bd83b97
URI: uuid:84e5e639-5c02-850c-87ea-5ce32bd83b97
Microsoft GUID syntax: {84E5E639-5C02-850C-87EA-5CE32BD83B97}
C++ struct syntax: { 0x84e5e639, 0x5c02, 0x850c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.176651800922903141008600634914988637079
As OID (Microsoft): 1.2.840.113556.1.8000.2554.34021.58937.23554.34060.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9576313316704421132.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2229659193.1543669004.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.34021.58937.23554.34060.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x84e5e6395c0250c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x84e5e639]
Custom data block2 (16 bit): [0x5c02]
Custom data block3 (12 bit): [0x50c]
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: [0x84e5] 0b1000010011100101
Milliseconds: [0xe6] 901 (deviation -2ms..2ms)
Seconds: [0x39] 57
Minute of day: [0x025c] 604 (10:03)
Day of year: [0x0c5] 197 (Day=16, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-16 10:03:57'901 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing