Interpret a UUID
Back
Your input: a8e85d36-6a04-8c0d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:a8e85d36-6a04-8c0d-87ea-5ce32bd83b97
URI: uuid:a8e85d36-6a04-8c0d-87ea-5ce32bd83b97
Microsoft GUID syntax: {A8E85D36-6A04-8C0D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xa8e85d36, 0x6a04, 0x8c0d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.224516806738270770158532371401733061527
As OID (Microsoft): 1.2.840.113556.1.8000.2554.43240.23862.27140.35853.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12171080481257065485.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2833800502.1778682893.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.43240.23862.27140.35853.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xa8e85d366a04c0d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xa8e85d36]
Custom data block2 (16 bit): [0x6a04]
Custom data block3 (12 bit): [0xc0d]
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: [0xa8e8] 0b1010100011101000
Milliseconds: [0x5d] 364 (deviation -2ms..2ms)
Seconds: [0x36] 54
Minute of day: [0x046a] 1130 (18:49)
Day of year: [0x0dc] 220 (Day=8, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-08 18:49:54'364 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing