Ticker Symbols, ISIN, CUSIP: How Instruments Are Identified

None of them is fake: financial instruments carry multiple identifiers operating at different levels, and knowing which level each one names is the difference between finding the security you meant and buying its cousin. This article teaches the identifier stack: tickers (short, human-friendly, exchange-local), ISIN (the international standard naming the security itself), CUSIP and SEDOL (the national numbering systems inside the ISIN), and the newer open identifiers (FIGI) that name each listing. The payoff is practical: why one company legitimately appears many times in a search, why the ticker alone can be ambiguous or even recycled, and which identifier answers which question — the small piece of data literacy that prevents a surprisingly common class of real-world mistakes.

Tickers: short, local, and not as unique as they look

A ticker symbol is the short trading mnemonic — one to five or so characters — under which an instrument trades on a particular exchange. Tickers are optimised for humans and screens, and their conventions are local dialects: US listings use bare letters (with suffix conventions for share classes and security types that vary by venue and vendor — a dot or hyphen before a class letter, for instance); London tickers historically carry different lengths and forms; continental European venues have their own styles; and the same company's listings on different exchanges usually carry different tickers. Three ambiguities make tickers unreliable as global names. Scope: a ticker is only unique per exchange — the same letters can name entirely unrelated companies on different venues worldwide, so a ticker without its exchange (the "TICKER on VENUE" pair, or vendor codes like exchange suffixes) is an incomplete address. Recycling: when a company delists, merges, or renames, its ticker can eventually be reassigned to a different firm — historical data keyed by ticker alone can silently splice two companies together, a real hazard in downloaded datasets and one reason serious databases key on other identifiers. Similarity traps: the documented record includes episodes of investors buying the wrong security because its ticker resembled a famous one — near-miss symbols spiking on another company's news — which is why this portal's standing habit is to confirm the full identity (name, exchange, security type) before acting on any symbol. Tickers are excellent handles and poor passports; the passports come next.

ISIN, CUSIP, SEDOL: the formal numbering stack

The ISIN (International Securities Identification Number, ISO 6166) is the global standard identifier for a security: twelve characters — a two-letter country prefix, a nine-character national securities number (NSIN), and a single check digit computed from the rest, so systems can catch most typos mechanically. Example structure (fictional): SK + 012345678 + check digit. ISINs are issued through national numbering agencies coordinated by ANNA (the Association of National Numbering Agencies), and the national number inside the ISIN is often a pre-existing local identifier: in the US and Canada that slot is the CUSIP — the nine-character North American numbering system (operated by CUSIP Global Services) that predates ISIN and remains the working identifier across US market plumbing; in the UK and Ireland it is the SEDOL (Stock Exchange Daily Official List number, operated by the London Stock Exchange). So a US stock's ISIN literally contains its CUSIP with US in front and a check digit behind — one security, nested identifiers. The crucial subtlety is what an ISIN does and does not distinguish: it names the security, not the listing. A share traded on five exchanges has one ISIN and five tickers — so the ISIN answers "is this the same security?" while the ticker-plus-exchange answers "which market and currency am I trading it in?" For the listing level, the market's newer open standard is the FIGI (Financial Instrument Global Identifier), which assigns identifiers down to the individual listing and is freely licensable — part of a broader, ongoing industry conversation about open versus fee-based identifier systems, reported here simply as the landscape. Two adjacent facts complete the map: identifiers name instruments, not companies — one company issues many securities (share classes, bonds each with their own ISIN/CUSIP, listed derivatives with their own coding schemes), so "the ISIN of the company" is not a well-formed request; and depositary receipts are different securities — an ADR/GDR representing a foreign share carries its own ISIN, distinct from the underlying share's, which is exactly the kind of same-company-different-security distinction the identifier stack exists to keep straight.

Why one company shows up five times — and which result answers which question

Assembled, the stack decodes the crowded search result. A large multinational may legitimately appear as: its home listing (home ticker, home ISIN); secondary listings on other exchanges (different tickers, often the same ISIN, different trading currencies); a depositary receipt in another market (different ticker and different ISIN); plus its bonds and other securities (their own identifiers entirely). Every row is real; they differ in venue, currency, trading hours, liquidity, and sometimes in what the security is. The literacy checklist, stated as mechanics: match the security with the ISIN (same ISIN = same security wherever it trades); match the listing with ticker-plus-exchange (or a listing-level identifier), because venue determines currency, hours, local liquidity, and which data feed's prices you are looking at; and treat name-only or ticker-only searches as the start of identification, not the end. For data work the same checklist scales up: historical datasets keyed by ISIN (or listing-level identifiers) survive renames and ticker recycling that silently corrupt ticker-keyed data — a small convention choice that quietly determines whether a dataset means what its user thinks it means, which is this pillar's recurring theme and the note on which the reading-the-data cluster closes.