Logistics companies sometimes embed a check letter in tracking IDs to detect typos. If 172165o5 were a tracking number, the carrier might treat o as a valid checksum character.
Let’s dissect 172165o5:
Unlike purely numeric IDs (e.g., 17216505), the presence of o restricts its use to systems that allow mixed-case or lowercase letters, often base-36 encoding or custom hash abbreviation.
For internal tools, engineers often generate shorter alphanumeric keys using base-36 encoding. The decimal value of 172165o5 (in base-36) would be different from a purely numeric interpretation.





