Flightradar24 Airport Boards Scraper avatar

Flightradar24 Airport Boards Scraper

Pricing

from $1.60 / 1,000 board entry chargeds

Go to Apify Store
Flightradar24 Airport Boards Scraper

Flightradar24 Airport Boards Scraper

Get airport arrivals, departures, and on-ground boards from Flightradar24. Talks directly to Flightradar24's own gRPC/REST APIs, no login needed. Split from the mature, published flightradar24-all-in-one-api for a focused, single-purpose workflow.

Pricing

from $1.60 / 1,000 board entry chargeds

Rating

0.0

(0)

Developer

Romy

Romy

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

22 days ago

Last modified

Categories

Share

What does Flightradar24 Airport Boards Scraper do?

Flightradar24 Airport Boards Scraper fetches, for one airport id, the airport's own info (location, weather, stats, photos, runways) plus its arrivals, departures, and on-ground boards — paginating each board automatically until it runs out of results or hits your maxPages. Every flight entry becomes one dataset row, tagged with which board it came from and its page number.

It talks directly to Flightradar24's legacy REST API (mobile.flightradar24.com) — the same one the official Android app uses (no login, no API key, anonymous accesstoken). This is the airport-boards slice of Flightradar24 All-in-One API, split out as its own focused Actor.

Why use Flightradar24 Airport Boards Scraper?

  • One call, full picture — airport info plus all three boards (arrivals/departures/on-ground) in one run
  • Automatic pagination — loops page for you, stopping cleanly once a page comes back empty
  • No account needed — every read request works fully anonymously
  • Use cases: airport traffic dashboards, delay/on-time monitoring, aviation research, flight-tracking apps

Input

FieldTypeDefaultDescription
airportIdstring—, requiredFlightradar24 airport id, e.g. "631" for Jakarta Soekarno-Hatta (CGK).
includeAirportInfobooleantrueFetch and push the airport's own info as one dataset row.
includestring"images,weather,stats,runways"Sections to include in the airport-info row. Only used when includeAirportInfo is on.
boardTypesstring[]["arrivals","departures","on-ground"]Which boards to fetch and paginate.
maxPagesinteger3Stop paginating a board after this many pages (per board type), or sooner if empty.

Example:

{
"airportId": "631",
"includeAirportInfo": true,
"boardTypes": ["arrivals", "departures", "on-ground"],
"maxPages": 3
}

Output

One dataset row per airport-info request and per flight entry.

Airport info row:

{
"type": "airport-info",
"airportId": "631",
"info": {
"info": { "id": 631, "name": "Jakarta Soekarno Hatta International Airport", "iata": "CGK", "icao": "WIII" },
"images": [{ "thumbnail": "https://cdn.jetphotos.com/200/5/1105926_1744548517_tb.jpg" }],
"weather": { "condition": "cloudy", "temperature": 32 },
"stats": { "summary": { "totalFlights": 7045 } },
"runways": []
}
}

Arrivals/departures row:

{
"type": "arrivals",
"airportId": "631",
"page": 1,
"id": 5857308153,
"flight": { "id": "416f3fb7", "number": "IU311", "callsign": "SJV311" },
"status": { "name": "landed", "color": "green", "isAmbiguous": false, "live": true },
"scheduledTime": 1788150600,
"estimatedTime": 1788150481,
"airlineId": 1693,
"airline": "Super Air Jet",
"aircraftType": "A320"
}

On-ground row (a different shape — no status/scheduledTime, has landedTime and aircraft):

{
"type": "on-ground",
"airportId": "631",
"page": 1,
"id": 5857308153,
"flight": { "id": "416f3fb7", "number": "IU311", "callsign": "SJV311" },
"landedTime": 1788150481,
"aircraft": {
"registration": "PK-SGA",
"type": "A320",
"name": "Airbus A320-232",
"registeredOwners": "Super Air Jet"
}
}

Known limitations

  • arrivals/departures/on-ground only accept 100 results per page. Flightradar24's server validates limit against a fixed allow-list rather than an arbitrary range — 10/25/50/200 all get rejected with HTTP 422, only 100 works — so this Actor hardcodes it. maxPages is the only pagination control exposed.
  • Airport search/lookup by name isn't included here — use Flightradar24 All-in-One API's /search to find an airportId.
  • Live-map, flight-detail, follow-flight, and airport-disruptions endpoints are separate spin-off Actors — this one is airport-boards-only.

Pricing

This Actor uses Pay Per Event billing: charged $0.003 per row pushed to the dataset — one airport-info row plus one row per flight/board entry returned (event board-entry, FREE tier price — lower on paid plans).

FAQ

Does this require a Flightradar24 account? No. The Actor uses the same anonymous data feed the Flightradar24 mobile app uses — no login, no API key.

Is this official? No. This is an independent tool using Flightradar24's internal APIs, reverse-engineered from the public Android app. Use responsibly and in accordance with Flightradar24's Terms of Service.

Need a custom integration? Contact me at romysaputrasihanandaa@gmail.com or hire me on Fiverr.