Interpret a UUID
Back
Your input: a3aa8614-8f00-8b0b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:a3aa8614-8f00-8b0b-87ea-5ce32bd83b97
URI: uuid:a3aa8614-8f00-8b0b-87ea-5ce32bd83b97
Microsoft GUID syntax: {A3AA8614-8F00-8B0B-87EA-5CE32BD83B97}
C++ struct syntax: { 0xa3aa8614, 0x8f00, 0x8b0b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.217549573250599360615395686993781865367
As OID (Microsoft): 1.2.840.113556.1.8000.2554.41898.34324.36608.35595.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11793385997079710475.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2745861652.2399177483.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.41898.34324.36608.35595.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xa3aa86148f00b0b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xa3aa8614]
Custom data block2 (16 bit): [0x8f00]
Custom data block3 (12 bit): [0xb0b]
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: [0xa3aa] 0b1010001110101010
Milliseconds: [0x86] 525 (deviation -2ms..2ms)
Seconds: [0x14] 20
Minute of day: [0x008f] 143 (02:22)
Day of year: [0x0bb] 187 (Day=6, 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-06 02:22:20'525 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing