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

Scrapes the geostationary satellite fleet from SatBeams.com — one record per satellite with orbital slot, operator, NORAD/Cospar IDs, beacon frequencies, and named footprint beams. For VSAT engineers and capacity brokers.

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

9 days ago

Last modified

Share

Scrapes the complete geostationary satellite fleet from SatBeams.com — one structured record per satellite with orbital slot, operator, manufacturer, NORAD/Cospar IDs, beacon frequencies, and named footprint beam coverage.

What it does

Performs a two-stage crawl:

  1. Index — fetches /satellites (optionally filtered by status), parses the satellite listing table to discover detail page URLs
  2. Detail — fetches each /satellites?norad=NNNNN page and extracts the full satellite specification

Each output record includes the complete operational profile: orbital position, operational status, operator, manufacturer, launch details, beacon transponder frequencies, and named footprint/coverage beam zones.

Use cases

  • VSAT and teleport engineers researching satellite capacity by orbital slot
  • DTH (Direct-to-Home) operators mapping available footprint beams
  • Satellite capacity brokers comparing operators and assets by position
  • Competitive intelligence on geostationary fleet composition
  • Cross-referencing with NORAD/TLE orbital element data from other datasets

Input

FieldTypeDescription
maxItemsintegerMaximum number of satellites to scrape. Each satellite = one detail page. Leave blank to scrape all ~650 satellites. Default: 10
statusFilterstringFilter by operational status: active, planned, moving, testing, retired, deorbited, disabled, failed. Leave blank for all statuses.

Output

One record per satellite with these fields:

FieldTypeDescription
satellite_namestringFull satellite name as listed on SatBeams
norad_idintegerNORAD catalog number — joins to TLE/orbital element datasets
intl_designatorstringInternational (COSPAR) designator, e.g. 2019-049B
orbital_positionstringOrbital slot, e.g. 62° E
statusstringOperational status: active, planned, moving, testing, retired, deorbited, disabled, failed
operatorstringSatellite operator / owner
manufacturerstringSpacecraft bus manufacturer
launch_datestringLaunch date
launch_mass_kgintegerLaunch mass in kilograms
dimensionsstringPhysical dimensions (where available)
power_wattsstringElectrical power in watts (where available)
expected_lifetimestringDesign/expected operational lifetime
launch_vehiclestringLaunch vehicle name
launch_sitestringLaunch site name
beacon_frequenciesstringBeacon transponder frequencies in MHz (comma-separated)
footprint_beamsstringNamed coverage beam/zone names (comma-separated, where published)
detail_urlstringSource URL on SatBeams for this satellite

Example output

{
"satellite_name": "Intelsat 39 (IS-39)",
"norad_id": 44476,
"intl_designator": "2019-049B",
"orbital_position": "62 E",
"status": "active",
"operator": "Intelsat",
"manufacturer": "Boeing",
"launch_date": "6-Aug-2019",
"launch_mass_kg": 6600,
"dimensions": "",
"power_watts": "",
"expected_lifetime": "15 yrs.",
"launch_vehicle": "Ariane 5 ECA",
"launch_site": "Guiana Space Center",
"beacon_frequencies": "3948.5, 3949, 3953, 3953.5, 3951, 10951.0R, 11699.5R",
"footprint_beams": "C-band East Hemi beam (active), C-band Europe beam (active), C-band West Hemi beam (active), Ku-band Europe beam (active), Ku-band Middle East beam (active)",
"detail_url": "https://www.satbeams.com/satellites?norad=44476"
}

Notes

  • Approximately 650 satellites in the SatBeams index across all statuses (~400 active)
  • The actor uses polite request throttling (2-second delay between requests) to respect SatBeams as a community resource
  • beacon_frequencies and footprint_beams are only populated where SatBeams publishes the data — not all satellites have complete information
  • The norad_id field is the standard join key to link records with TLE orbital element datasets