SatBeams Satellite Operator & Footprint Scraper avatar

SatBeams Satellite Operator & Footprint Scraper

Pricing

Pay per event

Go to Apify Store
SatBeams Satellite Operator & Footprint Scraper

SatBeams Satellite Operator & Footprint Scraper

Fetch the full SatBeams satellite catalog — every orbit (LEO/GEO/MEO/HEO), ~16.8k satellites. One record per satellite with orbit, status, operator, NORAD/Cospar IDs, launch details, and GEO orbital slot. For VSAT engineers, capacity brokers, and space-industry analysts.

Pricing

Pay per event

Rating

0.0

(0)

Developer

BowTiedRaccoon

BowTiedRaccoon

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Get the complete SatBeams satellite catalog from SatBeams.com — every orbit class (LEO, GEO, MEO, HEO), roughly 16,800 satellites — as clean, structured, dataset-ready records. One row per satellite with orbit, status, operator, manufacturer, NORAD/COSPAR IDs, launch details, and the GEO orbital slot.

What it does

Returns the full satellite fleet in a single run — current and up to date. Each record carries the operational profile you need to analyze, join, or feed downstream: orbit class, operational status, operator, spacecraft manufacturer and platform, launch vehicle and site, mass, expected lifetime, and (for geostationary satellites) the orbital position. Filter the whole catalog down to a single status, or pull everything at once.

Use cases

  • VSAT and teleport engineers researching satellite capacity by orbital slot
  • Space-industry analysts tracking active vs. decayed/deorbited fleet composition
  • Satellite capacity brokers comparing operators and assets by position
  • Competitive intelligence across LEO constellations and GEO operators
  • Cross-referencing with NORAD/TLE orbital element data from other datasets

Input

FieldTypeDescription
maxItemsintegerMaximum number of satellites to return. Leave blank (or 0) to return the full fleet (~16.8k).
statusFilterstringFilter by operational status: active, decayed, retired, deorbited, failed, disabled, moving, testing. Leave blank for all statuses.

Output

One record per satellite with these fields:

FieldTypeDescription
satellite_namestringFull satellite name
norad_idintegerNORAD catalog number — joins to TLE/orbital element datasets
intl_designatorstringInternational (COSPAR) designator, e.g. 2017-038A
statusstringOperational status: active, decayed, retired, deorbited, failed, disabled, moving, testing
orbitstringOrbit class: LEO, GEO, MEO, or HEO
orbital_positionnumberGEO orbital slot in degrees (positive = east, negative = west); null for non-GEO
operatorstringSatellite operator / owner
manufacturerstringSpacecraft bus manufacturer (GEO records)
modelstringSpacecraft platform / bus model (GEO records)
launch_datestringLaunch date (ISO 8601)
launch_mass_kgnumberLaunch mass in kilograms
dry_mass_kgnumberDry mass in kilograms
expected_lifetimestringDesign/expected operational lifetime in years
launch_vehiclestringLaunch vehicle name
launch_sitestringLaunch site name
beacon_frequenciesstringBeacon frequencies, as published
updatedstringTimestamp of the last catalog update for this satellite

Example output

{
"satellite_name": "BulgariaSat-1",
"norad_id": 42801,
"intl_designator": "2017-038A",
"status": "active",
"orbit": "GEO",
"orbital_position": 1.9,
"operator": "BulgariaSat",
"manufacturer": "Intuitive Machines (SSL/MDA/Maxar/Lanteris)",
"model": "LS-1300",
"launch_date": "2017-06-23T00:00:00Z",
"launch_mass_kg": 3669,
"dry_mass_kg": null,
"expected_lifetime": "15+ yrs.",
"launch_vehicle": "Falcon 9 Block 5",
"launch_site": "Cape Canaveral SFS",
"beacon_frequencies": null,
"updated": "2026-07-24T03:10:52"
}

Notes

  • Coverage spans the full SatBeams catalog across every orbit — not just geostationary.
  • orbital_position, manufacturer, and model are geostationary-specific and are null for LEO/MEO/HEO satellites.
  • Fields are populated only where SatBeams publishes the data — not every satellite has a complete profile.
  • norad_id is the standard join key to link records with TLE orbital element datasets.