TLE Format Explained: How to Read Satellite Orbit Data

The TLE format (two-line element set) is a standardised, fixed-width text format that encodes a satellite’s orbital elements at a reference time called the epoch. A TLE is neither a live position report nor, by itself, a collision warning: it supplies inputs for calculating an orbit, not a direct measurement of where an object is now.

SGP4 (Simplified General Perturbations 4), an orbital prediction model, uses those inputs to estimate an object’s position and velocity at other times. Orbital Radar’s live catalogue contains 32,118 objects as of 12 November 2026. Orbital Radar tracking data lists 16,694 active satellites as of 12 November 2026.

This guide explains how to identify each field, interpret unusual number formats and run a prediction without mistaking its output for certainty. You will also learn to judge the limitations imposed by ageing data and changes to an orbit. Orbital Radar’s tracking-data guide provides supporting context for understanding how orbital inputs become the positions shown on a tracking map.

What does a two-line element set actually describe?

A two-line element set (TLE) describes a satellite’s orbit through mean orbital elements: parameters defined for a particular mathematical model, rather than a record of its position at every instant. The TLE format encodes these elements in fixed-width text, with each field occupying assigned character positions, and gives a reference time called the epoch.

“Mean” matters because these elements are not simply a snapshot of an ideal ellipse fitted to the satellite’s instantaneous motion. They are designed for use with SGP4 (Simplified General Perturbations 4), the mathematical model that converts them into predicted positions while accounting for orbital disturbances.

Created by NORAD (North American Aerospace Defense Command) in the 1960s, the format became a foundation of public satellite tracking. That history does not mean NORAD alone maintains every modern catalogue or distributes every TLE. A complete TLE has two mandatory data lines; an optional preceding satellite-name line is often called line 0.

Orbital Radar tracking data lists 16,694 active satellites as of 12 November 2026. Public orbital elements help make such large populations trackable, although not every catalogue entry necessarily has a public TLE; Orbital Radar’s tracking-data guide provides context for understanding these orbital descriptions.

How is the TLE format laid out, column by column?

The TLE format consists of two 69-character data lines: each field occupies fixed columns, including spaces, and each line ends with a checksum digit. Column numbers below start at 1; the optional satellite-name line is not part of either data line.

TLE column referenceLineColumnsFieldUnits and parsing notes11Line numberLiteral 113–7Satellite catalogue identifierUsually numeric; Alpha-5 encoding can include a leading letter18ClassificationLetter; U means unclassified110–11Launch yearTwo digits112–14Launch numberLaunch sequence within that year115–17Launch pieceLetter code; may contain padding spaces119–20Epoch yearTwo digits121–32Epoch dayDay of year, including fractional day134–43First mean-motion derivative ÷ 2Revolutions/day²; explicit decimal point145–52Second mean-motion derivative ÷ 6Revolutions/day³; implied decimal and compact exponent154–61BSTAR drag parameterInverse Earth radii; implied decimal and compact exponent163Ephemeris typeInteger model code165–68Element set numberInteger169ChecksumSingle digit21Line numberLiteral 223–7Satellite catalogue identifierMust match line 129–16InclinationDegrees218–25Right ascension of ascending nodeDegrees227–33EccentricityDimensionless; decimal point omitted235–42Argument of perigeeDegrees244–51Mean anomalyDegrees253–63Mean motionRevolutions/day264–68Revolution number at epochInteger269ChecksumSingle digit

Unlisted columns are separator spaces; retain them and any padding within fields. Splitting only on whitespace is unreliable because fields can touch, contain spaces or omit decimal points: parse by column position instead.

The catalogue identifier, commonly called the NORAD ID, identifies the tracked object. The international designator in line 1, columns 10–17, instead identifies its launch year, launch sequence and launch piece.

To verify each checksum, sum numerical digits in columns 1–68, count each minus sign as one, ignore other characters and take the result modulo 10 (the remainder after division by 10). A match detects some transcription errors; it establishes neither orbital accuracy nor authenticity.

Orbital Radar tracking data lists 16,694 active satellites as of 12 November 2026. Orbital Radar's live catalogue contains 32,118 objects, including debris, as of 12 November 2026. Orbital Radar’s tracking-data guide provides context for interpreting orbital records.

How do you read the epoch and other fields on line 1?

Line 1 identifies the object, dates its orbital solution and records drag-related parameters and bookkeeping fields. Read it as fixed-width fields: spaces and character positions matter.

The catalogue identifier is the object's NORAD catalogue number, not its launch number. Classification is usually U (unclassified). The international designator identifies the launch: a two-digit launch year, that year's launch sequence number and a letter suffix identifying the piece associated with that launch.

The epoch uses the pattern YYDDD.dddddddd: YY is the year, DDD the day of year, and the decimal fraction the elapsed portion of that day in UTC (Coordinated Universal Time). Day 001 is 1 January; .5 means noon. The legacy year convention assigns 57–99 to 1957–1999 and 00–56 to 2000–2056.

The next fields store the first derivative of mean motion (orbital revolutions per day) divided by two, and its second derivative divided by six. These describe rates of change, but SGP4 (Simplified General Perturbations 4), the prediction model used with TLEs, does not use either field directly.

The second-derivative and BSTAR fields use implied decimals and compact scientific notation. As a labelled format pattern, +MMMMM-E means +0.MMMMM × 10−E: the mantissa's decimal point and the exponent marker are omitted. BSTAR is a fitted drag-related parameter, not a direct atmospheric-density measurement.

Ephemeris type identifies the model convention and is normally 0 in public TLEs. The element-set number labels the solution's issue; it is not an accuracy score. Orbital Radar's tracking-data guide provides context for using these records.

Orbital Radar's live catalogue contained 32,118 objects on 12 November 2026. Orbital Radar tracking data listed 16,694 active satellites on 12 November 2026.

What do the orbital elements on line 2 mean?

Line 2 describes the orbit’s orientation and shape, the satellite’s position within it, its orbital rate and its revolution count at the epoch (the reference time). Its angular fields use degrees; mean motion uses revolutions per day.

Picture this orbit diagram: equatorial plane → northbound crossing → tilted orbital plane → perigee → satellite. The northbound crossing is the ascending node; perigee is the orbit’s closest point to Earth. The plane’s tilt and direction are separate from the satellite’s position within it.

• Inclination measures the orbital plane’s tilt relative to Earth’s equatorial plane.
• Right ascension of the ascending node locates that northbound crossing, measured around the equatorial plane from a reference direction towards the vernal equinox.
• Eccentricity describes how elongated the orbit is. Its TLE field has an implied leading decimal point: read the digits as a fraction, not a whole number.
• Argument of perigee measures the angle within the orbital plane from the ascending node to perigee, in the direction of motion.
• Mean anomaly specifies orbital phase at the epoch using an idealised, uniformly increasing angle. It is not the satellite’s directly observed angle along its orbit.
• Mean motion gives revolutions per day. The approximate orbital period in minutes is 1,440 ÷ mean motion.
• Revolution number at epoch records the orbit count associated with that reference time.

These are mean elements, not an exact instantaneous ellipse: they are designed for use with SGP4 (Simplified General Perturbations 4), the associated prediction model. Orbital Radar’s tracking-data guide provides context for interpreting them.

How does SGP4 turn a TLE into a satellite position?

SGP4 (Simplified General Perturbations 4) turns a TLE into an estimated satellite position and velocity by evolving its orbital elements from their epoch to a chosen prediction time. This is propagation: calculating an estimated orbital state at another time.

First, parse the fixed-width fields and validate the element set, including line identifiers, matching satellite identifiers, checksums and field ranges. Interpret the epoch, select the prediction time using a consistent time convention, then pass the elements to a tested SGP4 implementation. Inspect its error status before using the result: numerical output alone does not establish that propagation succeeded.

TLEs contain mean elements, with short-period orbital variations handled through the intended model rather than recorded as an instantaneous orbit. SGP4 accounts for perturbations (departures from ideal orbital motion), including effects of Earth’s shape and atmospheric drag. Putting TLE elements directly into a generic two-body calculator, which assumes an isolated Earth and satellite, will not reproduce their intended predictions.

Standard SGP4 output uses TEME (True Equator, Mean Equinox), a reference frame rather than an Earth-fixed map grid. Mapping that position onto Earth requires appropriate time handling and coordinate transformations that account for Earth’s rotation.

Combining the transformed orbital state with an observer’s latitude, longitude and height gives azimuth (compass direction), elevation (angle above the horizon) and range (distance). A geometric pass above the horizon is not necessarily visible: satellite illumination, sky darkness, weather and brightness also matter. Orbital Radar’s tracking-data guide provides context for interpreting these predictions.

How accurate is a TLE, and how quickly does it become outdated?

A TLE (two-line element set) has no universal positional accuracy or expiry interval. Its reliability depends on the orbit, observation quality, atmospheric drag, manoeuvres and elapsed time from its epoch (the instant the elements describe).

Element age and prediction horizon are different. Downloading a file now does not make its epoch current: the underlying solution may already be old. Predictions can run before or after the epoch, but reliability need not be equal in either direction, especially across a manoeuvre.

Orbital Radar tracking data lists 1,121 Starlink satellites as raising their orbits on 12 November 2026. Orbital Radar tracking data lists 208 Starlink satellites as deorbiting on 12 November 2026. Orbit raising and other propulsion manoeuvres change the trajectory, so an earlier element set can describe a path the satellite no longer follows. During low-altitude decay, changing atmospheric drag can also make older predictions misleading.

Use recent elements suitable for the prediction time, and compare successive solutions where available. Agreement is a useful consistency check, not proof of accuracy; Orbital Radar’s tracking-data guide provides context for interpreting orbital data.

A standard TLE contains no covariance matrix (a statistical description of orbital uncertainty and how its components are related). It therefore cannot independently establish a confident collision probability or precise re-entry time. Those assessments require additional uncertainty information, observations and modelling; a predicted position alone does not say how confidently it is known.

How can you check TLE-based tracking on Orbital Radar?

Check TLE-based tracking on Orbital Radar by matching the object’s catalogue identifier and establishing the time represented by its displayed position. The tracking-data guide provides context for interpreting orbital predictions; the TLE definition offers a concise reminder of the two-line element set format and its fields.

Use this practical checklist when interpreting a position:

• Match the catalogue identifier in the TLE to the object you intend to track, rather than relying on its name alone.
• Read the element epoch: the reference instant described by the orbital elements.
• Identify the prediction time: the instant for which the displayed position has been calculated.
• Distinguish a calculated orbital prediction from an observation that actually measured the object.

On a live display, establish whether the position represents the present or another selected time. Consult any available source or element-age information; an updating marker does not, by itself, establish that fresh observations are arriving.

Orbital Radar’s live catalogue contains 32,118 tracked objects as of 12 November 2026. That catalogue includes debris and rocket bodies as well as payloads, so a displayed point is not itself proof of an operational satellite.

How does TLE compare with OMM and precision orbit data?

OMM (Orbit Mean-Elements Message) is a more extensible alternative to the fixed-width TLE format, but it is not automatically more accurate. Developed through the Consultative Committee for Space Data Systems, OMM can carry mean orbital elements compatible with SGP4 (Simplified General Perturbations 4), the prediction model used with TLEs. Changing the container does not improve the underlying orbit solution.

Mean elements describe an orbit within a particular model rather than listing successive positions. A time-tagged position-and-velocity ephemeris instead supplies calculated states at specified times; operator-derived precision products can incorporate spacecraft tracking and manoeuvre information. Suitability depends on the reference frame (the coordinate system), force model (the physical effects included), update frequency and uncertainty information—not simply the file format.

Orbital Radar's live catalogue contains 32,118 objects as of 12 November 2026. Orbital Radar tracking data lists 16,694 active satellites as of 12 November 2026. That catalogue scale makes identifier handling an important practical difference between formats.

Legacy TLE fields constrain catalogue identifiers and use two-digit years, requiring software to interpret the century. Alpha-5 identifiers extend the legacy catalogue-number field using a letter, but older parsers may reject or misread them; support should not be assumed across providers. OMM avoids those particular fixed-width restrictions, although software must still interpret its metadata correctly. Orbital Radar's tracking-data guide provides context for choosing between mean-element tracking and more detailed orbit products.

What mistakes should you avoid when using TLE data?

Avoid changing fixed-width spacing, mixing objects’ records or confusing processing errors with bad orbital data. Use this checklist before trusting a TLE (two-line element set) prediction.

• Preserve column positions: damaged spacing can shift fields. Confirm that both lines carry matching catalogue identifiers and valid checksums (error-detection digits); a valid checksum does not prove accuracy.
• Restore implied decimal points correctly, and preserve exponent signs in compact scientific notation. Losing a minus sign can radically change a value.
• Check UTC (Coordinated Universal Time) handling, day-of-year conversion and reference-frame conversion separately. Calendar mistakes and incompatible coordinate systems can produce discrepancies without the underlying elements being faulty.
• Use SGP4 (Simplified General Perturbations 4), the propagation model intended for TLEs, rather than feeding their model-specific mean elements into an incompatible orbit calculator.
• Do not treat mean motion as an exact altitude measurement, or the revolution counter as a permanent lifetime total.

Orbital Radar’s live catalogue contains 32,118 objects as of 12 November 2026. Orbital Radar tracking data records 18 active close approaches as of 12 November 2026.

Public tracking and pass planning are not safety-critical conjunction assessment (analysis of close approaches). A close-looking map encounter needs positions at consistent times, uncertainty information and specialist analysis before it can be described as a collision risk. Orbital Radar’s tracking-data guide provides context for interpreting public predictions.

Key takeaways

• A TLE encodes model-specific mean orbital elements at an epoch, not a continuously measured satellite position.
• Read both fixed-width lines carefully: spaces, implied decimals, exponent signs and checksums all matter.
• Use a compatible SGP4 implementation and correct time and coordinate transformations to turn elements into useful predictions.
• Recent elements improve tracking, but a TLE alone cannot establish collision probability or guarantee a precise re-entry time.