N2YO Live Real-Time Satellite Tracking Directory

N2YO Live Real-Time Satellite Tracking Directory is the orbital census of the cable satellite data hub: 35,103 cataloged objects counted live as of 21 August 2026, each identified by NORAD catalog number and carrying a computed state vector - sub-satellite latitude and longitude, altitude in kilometers and miles, orbital speed in kilometers and miles per second, azimuth, elevation, right ascension, declination and orbital period. Field definitions were verified against live captures during cataloging, and the dataset scores 8 out of 10 on Datadory's quality rubric.

Three browse axes organize the population: by category - ISS, Chinese Space Station, Starlink, the operational GPS, Glonass, Galileo and BeiDou constellations, Military, Iridium, Globalstar, Geostationary, Weather, Amateur radio and more - by launch date, and by country or owner. A Just launched feed tracks fresh arrivals, and it reads as a Starlink deployment log more often than not.

Get a sample of this dataset cut to your constellations, countries or launch windows.

One telemetry row, keyed to the object cataloged as NORAD 25544, exactly as the fourteen documented fields land:

norad id     : 25544
local time   : 21-Aug-2026 09:47:12
utc          : 21-Aug-2026 04:17:12
latitude     : 12.98 deg
longitude    : 77.60 deg
altitude     : 417.42 km  (259.38 mi)
speed        : 7.66 km/s  (4.76 mi/s)
azimuth      : 245.3 deg
elevation    : 32.1 deg
right asc.   : 18h 22m
declination  : +12.4 deg
period       : 92.68 min

Read the anatomy rather than the single object. Dual clocks on every row - local time and UTC - let a sighting reconcile against either a ground station's wall clock or a mission log. Position and the celestial coordinates are intrinsic; altitude and speed arrive in both unit systems; and the observer-relative pair, azimuth and elevation, is what turns an ephemeris into a pointing instruction. A 92.68-minute period marks the near-Earth regime, where the crowded shells sit and most operational attention concentrates. Multiply one row by 35,103 objects and by a capture schedule, and the directory becomes a fleet monitor.

Fourteen documented fields carry every telemetry row, with definitions verified against live captures during cataloging. Every field in the table below carries a worked example, all drawn from the single NORAD 25544 capture shown above. Readouts exposed beside the telemetry table arrive populated but ship without a fixed worked example - local sidereal time among them - so they sit under additional fields on request, together with derived columns: position histories assembled from scheduled captures, per-category population counts and constellation roll-ups keyed on the NORAD number.

• Geography: Worldwide. Sub-satellite latitude and longitude, altitude, speed and period are properties of the object itself; azimuth and elevation are observer-relative and resolve against whichever site you name - one catalog serves a Florida earth station and a Singapore teleport from the same rows.
• Temporal: Live and current-state. Each row mirrors the object's computed position now, and the catalog spans objects launched to present, from long-serving geostationary workhorses to last week's rideshare. No historical archive is published upstream, which is precisely what a daily, weekly or hourly cadence is for - scheduled captures assemble the trendline.
• Granularity: One row per cataloged object per observation instant. Addressing by NORAD number returns one object; walking a category or a country listing returns the whole cohort.

API, files, or your warehouse. Daily, weekly, or hourly.

Every delivery ships the complete field dictionary above, the sample rows and the coverage profile mapped to your scope, with rows keyed on the NORAD catalog number so consecutive pulls reconcile without remapping.

• Constellation and fleet monitoring - watch Starlink, Iridium, Globalstar or the GNSS operational shells object by object, catching new arrivals and reassignments through the Just launched feed rather than waiting on press releases.
• Ground-segment planning - azimuth and elevation resolved against a named site turn the catalog into pointing schedules and contact windows; integration patterns sit on the developers builders use cases page.
• Competitive intelligence - country and owner attribution plus launch-date cohorts make fleet growth and national programs measurable instead of anecdotal, as laid out on the competitive intel product teams use cases page.
• Research baselines - pair the live population against static censuses to measure drift between snapshots; the data scientists use cases page develops that workflow.
• Citation-grade fact-checking - quote a position, an altitude or a population count straight from a timestamped row when a story needs a number that holds up.

Datadory's routing for this dataset leads with three audiences:

1. Data Scientists & ML Engineers - one uniform per-object schema across 35,103 rows trains models and measures populations without per-source cleanup.
2. Competitive Intelligence & Product Teams - constellation-by-constellation presence tracking turns the catalog into a market-share ledger for space assets.
3. Developers & Data-Product Builders - stable NORAD-keyed rows drop into tracking features and dashboards with minimal mapping.

Investors & Quant Researchers, Journalists-Academics and telecom strategy groups follow: fleet composition and launch tempo read directly off the country, owner and launch-date axes.

Three honest gaps. First, history: the directory publishes current-state rows, so any trendline is assembled by capturing on a schedule - which is what the cadence options exist to automate, keyed on NORAD number. Second, the population moves: 35,103 objects stood as of 21 August 2026, and the figure shifts as launches and catalog maintenance land, so treat every count as the dated floor it was taken on. Third, geometry is split by design: intrinsic quantities - position, altitude, speed, period - hold anywhere, while azimuth and elevation require an observer location, so name your sites up front. None of this is hidden at delivery; say which gap bites your question and the sample comes back shaped around it.

The orbital shelf has depth beyond one directory. N2YO REST API v1 is the same catalog's structured counterpart - TLE lookup, one-second-step positions and pass predictions out to ten days. UCS Satellite Database freezes 7,560 operating satellites with owner, purpose, mass and contractor columns - the citable baseline this live directory drifts away from. SatBeams Satellite Coverage & Channel Database adds EIRP footprints across 500+ GEO positions, and SatIndex Daily Transponder Scan Database watches transponders rather than objects. When the broadcast side matters, KingOfSat European Satellite Zapping & Directory carries 25,839 channels across 162 countries - or read the vs KingOfSat comparison for the head-to-head. Everything above sits in the best cable-satellite datasets ranking.