🚦 TfL London Live Status Scraper

🚀 Export Transport for London's live status feed in seconds. Per-line service health for the Tube, Overground, Elizabeth line, DLR, buses, trams, river bus, cable car, and Santander Cycles, plus current disruptions and the full station catalogue. No sign-up, no manual scraping.

The TfL London Live Status Scraper exports the official Transport for London live status feed and returns up to 42 fields per record, depending on whether you fetch line statuses, disruptions, or station catalogues. The TfL feed is the canonical reference for London transit and powers Citymapper, the official TfL Go app, and dozens of accessibility and journalism projects.

The catalogue covers 10 transport modes across every London travel zone: London Underground (Tube), DLR, London Overground, Elizabeth line, National Rail services managed by TfL, the bus network, trams, river bus, the IFS Cloud cable car, and Santander Cycles. This Actor makes the live feed downloadable as CSV, Excel, JSON, or XML in under a minute. Filtering by transport mode runs server-side.

🎯 Target Audience	💡 Primary Use Cases
London transit-app developers, accessibility advocates, urban-planning teams, real-estate platforms, journalism teams, mobility researchers	Live service-status widgets, disruption alerts, station-accessibility audits, commuter dashboards, real-estate transit scoring, transport-equity research

📋 What the TfL London Live Status Scraper does

Three data modes, each across 10 transport modes:

• 🚇 Line status. Service health per line, with severity codes (1-20), human-readable descriptions, and active disruptions.
• ⚠️ Disruptions. Current incidents with category, description, affected routes, affected stops, and last-update time.
• 🚉 Stations. Full catalogue with NaPTAN IDs, lat/lon, accessibility info (lifts, boarding ramps, toilets, cash machines), and modes served.

Filter every mode by transport mode (Tube, DLR, Overground, Elizabeth line, National Rail, bus, tram, river bus, cable car, cycle).

💡 Why it matters: TfL serves more than 4 million weekday journeys. Live status data powers commuter apps, accessibility scoring, and journalism on service equity. Building your own pipeline means juggling multiple TfL data products and reconciling status codes. This Actor skips all of that.

📊 Data fields

Each record includes: additionalInfo, additionalProperties, address, affectedRoutes, affectedStops, bays, bearing, bikesAvailable, boardingRamps, cashMachines, category, categoryDescription, childStopCount, closureText, created, currentLocation, description, destinationName, destinationNaptanId, direction, disruptionCategory, disruptionDescription, disruptions, eBikes, emptyDocks, expectedArrival, forecastBand, forecastID, forecastSummary, forecastText, forecastType, free, fromDate, hasActiveDisruption, helpPoints, hubNaptanCode, icsCode, id, installDate, installed. These field names come straight from the actor's dataset schema, so what you see here is what lands in your dataset.

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🌐 Open the Actor. Go to the TfL London Live Status Scraper page on the Apify Store.
3. 🎯 Set input. Pick a data mode (line status, disruptions, stations) and a transport mode.
4. 🚀 Run it. Click Start and let the Actor pull the live feed.
5. 📥 Download. Grab your results in the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to downloaded TfL feed: 3-5 minutes. No coding required.

🔗 Recommended Actors

• 🚇 MBTA Live Transit Scraper - Boston transit routes, stops, vehicles, and predictions
• 🗺️ OSRM Routing Scraper - Driving, cycling, and walking routes anywhere
• 🌍 Carbon Intensity UK Scraper - UK grid carbon intensity in gCO2/kWh
• 🗺️ Nominatim OSM Scraper - Geocode addresses via OpenStreetMap
• 📰 Guardian Article Search Scraper - Search The Guardian's full article archive

💡 Pro Tip: browse the complete ParseForge collection for more transit and UK-data scrapers.

⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Transport for London or any of its affiliates. All trademarks mentioned are the property of their respective owners. Only publicly available open transit data is collected.

🆘 Need Help?

If you hit a bug, have questions about setup, or need a scraper we haven't built yet, open our contact form or write to parseforge@protonmail.com. We also take on paid custom data projects.

For faster answers, join our Discord. It's the best place to get support and suggest new actors.