Flightradar24 Live Map Scraper

What does Flightradar24 Live Map Scraper do?

Flightradar24 Live Map Scraper runs a single bounded query against Flightradar24's internal gRPC live feed (data-feed.flightradar24.com) and pushes one dataset row per result — no API key, no login, no scraping setup. It's the live-position slice of Flightradar24 All-in-One API, split out as its own focused Actor.

Three modes:

• live-feed — every flight currently inside a bounding box
• top-flights — the globally most-tracked flights right now (Flightradar24's own "scoreboard")
• nearest-flights — flights nearest a lat/lon, sorted by distance

Why use Flightradar24 Live Map Scraper?

• Real-time — positions update roughly every 1–3 seconds per flight on Flightradar24's side
• No account needed — talks to the same anonymous feed the free-tier Flightradar24 Android app uses
• One call, one result set — no pagination or streaming to manage; each run pushes a bounded snapshot and exits
• Use cases: aviation monitoring, airport-region traffic snapshots, flight-delay/research datasets, competitive intelligence on route activity

How it connects to the parent

This Actor reuses the parent's gRPC plumbing (fr24-grpc.ts — HTTP/2 framing, unary calls, protobuf loading) verbatim, and re-implements only the LiveFeed, TopFlights, and NearestFlights operations from the parent's fr24-feed.ts. It drops FlightDetails, FollowFlight, Playback, and LiveFlightsStatus — those stay in the full Flightradar24 All-in-One API.

Input

Field	Type	Default	Description
mode	string	—	Required. "live-feed" | "top-flights" | "nearest-flights"
north / south / west / east	number	—	Bounding box in decimal degrees. Required for live-feed.
limit	integer	varies	Max results. Default 1500 (live-feed), 50 (top-flights), 300 (nearest-flights).
maxage	integer	14400	Max age (seconds) of position data to include. live-feed only.
lat / lon	number	—	Center coordinate. Required for nearest-flights.
radius	integer	200000	Search radius in meters. nearest-flights only.

Example (live-feed, flights over Indonesia):

{
    "mode": "live-feed",
    "north": 6,
    "south": -11,
    "west": 95,
    "east": 141,
    "limit": 50
}

Output

One dataset row per flight (live-feed, nearest-flights) or scoreboard entry (top-flights).

live-feed row (real example field shape, from the parent's proven-working feed):

{
    "flightId": 1094013202,
    "lat": -5.815,
    "lon": 111.413,
    "track": 205,
    "alt": 38000,
    "speed": 476,
    "callsign": "PAS646",
    "onGround": false,
    "timestampMs": "1786924707066",
    "extraInfo": { "flight": "IP646", "reg": "PK-PWO", "type": "A320" }
}

nearest-flights row — the same Flight fields as above, flattened with the server-computed distance:

{
    "flightId": 1094013202,
    "lat": -5.815,
    "lon": 111.413,
    "callsign": "PAS646",
    "distanceMeters": 18342
}

top-flights row:

{
    "flightId": 1094013202,
    "liveClicks": 812,
    "totalClicks": 15230,
    "flightNumber": "IP646",
    "callsign": "PAS646",
    "fromIata": "CGK",
    "toIata": "SIN",
    "fullDescription": "Airbus A320-214"
}

Known limitations

• Three modes only — flight-details, follow-flight (live streaming), playback (history), and flights-status (batch refresh) are not exposed here; use the parent Flightradar24 All-in-One API for those.
• No auth for any mode, same as the rest of the parent's feed endpoints — the gRPC feed is called anonymously, exactly as the free tier of the Flightradar24 app does.
• nearest-flights distance is server-computed, in meters, as returned by Flightradar24 — not a client-side haversine calculation.

Pricing

This Actor uses Pay Per Event billing: charged $0.002 per flight/result row pushed to the dataset (event flight, FREE tier price — lower on paid plans). See the Actor's Pricing tab for current rates.