Every satellite has an identity
NORAD IDs and COSPAR designators

Search for the International Space Station and one source may display ISS (ZARYA), another may shorten it to ISS, and a historical document may emphasize the Zarya module. Those names are meaningful to people, but names alone are poor database keys. Spelling, punctuation, transliteration, ownership, and mission phase can all change how an object is labeled.

Operational catalogs therefore separate a human-readable name from machine-friendly identifiers. The ISS object commonly used in orbital data carries catalog number 25544 and International Designator 1998-067A. All three labels can refer to the same cataloged object, but each answers a different question.

The name answers, "What do people call it?" The catalog number answers, "Which record should I retrieve?" The International Designator answers, "Which launch and which piece from that launch is this object associated with?" Confusing those roles produces broken links, duplicate records, and incorrect satellite selections.

The number often called a NORAD ID, NORAD catalog number, satellite catalog number, or SSN number is a numerical key used to identify a record in the space-object catalog. For the ISS example, that key is 25544. A query using 25544 can retrieve the intended object even when a provider uses a slightly different name.

Despite the everyday word "satellite," the catalog is not limited to functioning spacecraft. Trackable payloads, spent rocket bodies, adapters, mission-related objects, and debris can receive catalog records. The number tells you which object record is meant; it does not tell you that the object is active, useful, owned by a particular country, or safe.

A catalog number is also not a launch sequence number. Number 25544 does not mean the 25,544th launch. Cataloging follows tracked objects, and one launch can produce several separately tracked objects. Conversely, a newly detected object may need additional observations before analysts can correlate it confidently with a known launch.

Within a data provider's catalog, the number is the practical lookup key. It normally remains associated with that record while names, orbital elements, and operational status evolve. That stability is why Jewawud uses the catalog number in Satellite Index detail URLs such as ISS record 25544.

The International Designator, frequently called a COSPAR ID, organizes objects by launch. Its full pattern is commonly written as YYYY-NNNPPP. The first four digits give the launch year, the three-digit block gives the launch sequence within that year, and the final letter group identifies a piece associated with that launch.

For 1998-067A, the year is 1998. The number 067 marks the 67th launch sequence assigned for that year. The letter A distinguishes one cataloged piece from other objects associated with that launch. Objects from the same launch can therefore share the 1998-067 stem while carrying different piece letters.

The piece suffix may contain more than one letter as the number of associated objects grows. It should not be interpreted too casually: A is not a universal promise that an object is the primary payload. The designator is an identification convention, not a complete description of mission role, ownership, or current condition.

A rocket does not always place one neat object in orbit. After launch, tracking networks may observe the payload, upper stage, payload adapter, lens covers, deployment hardware, or fragments. If observations show that these are separate orbiting objects, they can be represented by separate catalog records.

Those records need separate catalog numbers because each object has its own trajectory. Yet objects associated with the same launch can share the year and launch-sequence portion of the International Designator. The piece suffix then separates them. This makes the two identifier systems complementary: one points to an individual catalog record, while the other preserves launch lineage.

Lineage becomes particularly valuable when an unfamiliar object name appears in a tracker. A shared designator stem can reveal that several records came from the same launch even if one is a payload and another is a rocket body. It is a clue for investigation, not proof that all pieces still travel together. Small differences in separation velocity and atmospheric drag can spread them around Earth.

Catalog identifiers are comparatively stable. Orbital elements are time-dependent estimates. A Two-Line Element set contains a catalog number, but it also carries an epoch and parameters that describe the object's estimated motion around that time. New observations lead to new element sets while the catalog number remains the lookup key.

This distinction explains why copying an old TLE is not equivalent to preserving an object's identity. The record may still be correct, but its old orbital state becomes progressively less useful for present-time propagation. The TLE article explains how epoch and element fields are encoded, while the SGP4 article shows how those elements are propagated to a requested time.

Think of the identifier as a library card number and the orbital elements as a dated location estimate. The card number tells the system which object it is discussing. The elements tell the propagator where that object is expected to be, based on a particular fitted data set.

A sensor detection does not arrive with a name painted beside it. Radar, optical, and other tracking observations contain measured quantities tied to time and sensor geometry. Analysts and correlation systems compare those observations with predicted tracks and previous observations to decide whether they belong to an existing object or a newly tracked one.

When observations are correlated into a consistent track, they can support an orbit estimate and a catalog record. Associating that record with a launch may require additional evidence. During analysis, a public name or International Designator may be unavailable even though the object is being tracked.

The public catalog should not be treated as a perfect inventory of every object in space. Some objects are too small, too briefly observed, insufficiently correlated, withheld, or still under analysis. Cataloging is a continuing measurement and identification process, not a one-time roll call immediately after launch.

Names are excellent interface labels because people remember them. They are unsafe as the only identity field because they can contain aliases, abbreviations, punctuation changes, reused mission names, or translations. A search for "ISS" is friendly; a request for catalog number 25544 is precise.

A robust application stores the catalog number as the object key and treats the displayed name as metadata. When available, it also stores the International Designator for launch-based filtering and cross-reference. If the name later changes, bookmarks and internal relationships remain intact because the stable numerical key has not changed.

This design also prevents a common interface error: selecting a satellite by list position. Lists reorder whenever new objects are added or filters change. The visible row is temporary; the catalog identifier is what the click handler, URL, cache, and orbital request should carry.

In the legacy fixed-width TLE format, the catalog number occupies columns 3 through 7 on both lines. Line 1 also stores a shortened form of the International Designator: two digits for launch year, three for launch number, and up to three characters for the piece. Applications often reconstruct or receive the four-digit year in modern metadata.

The classic TLE layout has a five-character catalog-number field, which creates a limit as catalogs grow beyond 99,999. Modern General Perturbations data formats such as OMM, JSON, CSV, XML, and KVN can carry larger catalog numbers and clearer field names. Software should avoid assuming that every future catalog number will always fit a five-digit string.

Format and identity are separate concerns. A provider can offer the same object through TLE, JSON, or OMM. The surrounding syntax changes, while the catalog number continues to identify which object the record describes. Good import code parses the format explicitly rather than extracting identifiers through fragile string guesses.

The Jewawud Satellite Index is designed as a searchable reference layer. A visitor can begin with a familiar name, then inspect the catalog number, International Designator, object type, launch information, and available orbital record. The catalog number anchors the detail page so a new visitor arriving from Google knows which exact object is being described.

From there, live position is a different task. Jewawud Orbital Tracker (JOT) uses current orbital data and propagation to visualize where selected objects are expected to be. The Index answers "what object is this?" while JOT answers "where is its propagated position now?" The shared identifier lets both views refer to the same record.

This separation also improves search visibility. An index page can provide durable facts and definitions even when live orbital data refreshes frequently. A tracking page can focus on interaction without forcing every visitor to understand catalog conventions before seeing the map.

Start with the catalog number when you have it. It is normally the most precise public lookup key. Confirm the displayed name and object type, then check the International Designator to verify launch association.

If you only have a name, search broadly and verify narrowly. Compare catalog number, launch date, owner or country field, and object type before assuming two similarly named entries are the same spacecraft. Never resolve ambiguity from the name alone.

Check the epoch before using orbital elements. The correct identifier can still be paired with stale data. For current tracking, retrieve a recent element set from a trusted provider and propagate it with the matching model.

Preserve identifiers when exporting data. A screenshot or CSV containing only satellite names loses the strongest cross-reference. Include catalog number and International Designator when available so another researcher can reproduce the lookup.

Not every detected object immediately has a public name or International Designator. Analyst objects and uncertain correlations may remain incomplete while evidence accumulates. A blank field does not automatically mean the tracker is broken; it may represent the current limit of public identification.

A catalog entry is also not the same as international legal registration. The United Nations Register of Objects Launched into Outer Space records information submitted by states under the space-object registration framework. The International Designator helps cross-reference an object, but a NORAD catalog number does not itself prove UN registration, ownership, jurisdiction, or liability.

Finally, identical-looking identifiers from different sources should still be interpreted in context. Providers can differ in naming, status labels, update timing, or which data they publish. The identifier makes comparison possible; it does not guarantee that every surrounding field is equally current or authoritative.

CelesTrak: Two-Line Element Set Format documents the fixed columns used for satellite number and International Designator fields.

CelesTrak: General Perturbations Data Formats defines catalog-number and International Designator queries and explains modern format support beyond the legacy TLE field limit.

NASA: Zarya Module provides mission context for the first ISS element used in the worked identifier example.

United Nations Office for Outer Space Affairs: Online Index of Objects Launched into Outer Space explains the separate international registration framework.