Interpret a UUID
Back
Your input: a2f83016-5a05-810e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:a2f83016-5a05-810e-87ea-5ce32bd83b97
URI: uuid:a2f83016-5a05-810e-87ea-5ce32bd83b97
Microsoft GUID syntax: {A2F83016-5A05-810E-87EA-5CE32BD83B97}
C++ struct syntax: { 0xa2f83016, 0x5a05, 0x810e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.216623600264613864222631662398794644375
As OID (Microsoft): 1.2.840.113556.1.8000.2554.41720.12310.23045.33038.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11743188900926292238.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2734174230.1510310158.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.41720.12310.23045.33038.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xa2f830165a0510e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xa2f83016]
Custom data block2 (16 bit): [0x5a05]
Custom data block3 (12 bit): [0x10e]
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: [0xa2f8] 0b1010001011111000
Milliseconds: [0x30] 188 (deviation -2ms..2ms)
Seconds: [0x16] 22
Minute of day: [0x055a] 1370 (22:49)
Day of year: [0x0e1] 225 (Day=13, 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-13 22:49:22'188 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing