Interpret a UUID
Back
Your input: 3a8b9717-9e05-830b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:3a8b9717-9e05-830b-87ea-5ce32bd83b97
URI: uuid:3a8b9717-9e05-830b-87ea-5ce32bd83b97
Microsoft GUID syntax: {3A8B9717-9E05-830B-87EA-5CE32BD83B97}
C++ struct syntax: { 0x3a8b9717, 0x9e05, 0x830b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.77820017533864645922688106381627112343
As OID (Microsoft): 1.2.840.113556.1.8000.2554.14987.38679.40453.33547.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4218631603653804811.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.982226711.2651161355.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.14987.38679.40453.33547.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x3a8b97179e0530b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x3a8b9717]
Custom data block2 (16 bit): [0x9e05]
Custom data block3 (12 bit): [0x30b]
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: [0x3a8b] 0b0011101010001011
Milliseconds: [0x97] 592 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x059e] 1438 (23:57)
Day of year: [0x0b3] 179 (Day=28, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-28 23:57:23'592 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing