nexttrain.london is built with Next.js, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 16.2.6 | 6 Nov 2026 | |
| – | 6 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 6 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting1 | ||
| – | 6 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 6 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 6 Nov 2026 | |
| Security, WAF & Bot Protection2 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
eforward2.registrar-servers.comeforward3.registrar-servers.comeforward1.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.commaxine.ns.cloudflare.combob.ns.cloudflare.comv=spf1 include:spf.efwd.registrar-servers.com ~allgoogle-site-verification=RTBJBRtWfTs1qSjtmPeM5aQgiK9s-lNhA4JHGuTmB00User-Agent: * Allow: / Disallow: /api/ User-Agent: SemrushBot Disallow: / Host: https://nexttrain.london Sitemap: https://nexttrain.london/sitemap.xml
# Next Train — nexttrain.london
> Live London public-transport arrivals (Underground, Overground, DLR, Elizabeth line and buses) at the stops nearest a location, plus per-line strip-maps and per-route bus maps with live vehicle positions. Data from the Transport for London (TfL) Unified API and National Rail Enquiries where available.
Next Train is a fast, glanceable departure board. Give it a location and it shows the next trains/buses at the nearest TfL stops; open a bus route and it draws the route over a dark map with every live bus on it.
## Pages
- /: live train/tube/Overground/DLR/Elizabeth-line arrivals at your nearest stations (uses the browser's geolocation)
- /status: live service status (good service / delays / suspensions) for every tube and rail line — answers "is the {line} line running?"
- /buses: live bus arrivals at your nearest stops
- /lines, /stations, /routes: browsable indexes of every line, station and bus route
- /bus/{route}: map of a London bus route — e.g. /bus/28 — with its stops, direction, and live bus positions
- /line/{id}: strip-map of a rail line — e.g. /line/victoria, /line/elizabeth, /line/dlr
- /station/{id}: a station's live arrivals + the lines that serve it — e.g. /station/wood-green (Wood Green; raw ids redirect to canonical slugs); ids come from /api/station-search or /stations
- /developers: API overview for humans and agents
## For agents
- OpenAPI 3.1 spec: /openapi.json (machine-readable description of every endpoint below)
- All endpoints are GET, return JSON, need no API key, and are CORS-open (Access-Control-Allow-Origin: *) — usable from browsers and servers alike. Responses are cached; poll no faster than ~15s and prefer the enumeration endpoints to discover valid ids.
- Rate-limited per client IP. On HTTP 429, back off and honour the Retry-After header — the data is cached, so retrying faster only earns more 429s, not fresher results.
## Read-only JSON API (no API key needed; same data the site uses)
- GET /api/arrivals?lat={lat}&lon={lon} — nearest stations with next arrivals, grouped by platform
- GET /api/station-arrivals?id={id} — one station’s departures grouped by platform; use the id from /api/station-search
- GET /api/buses?lat={lat}&lon={lon} — nearest bus stops with upcoming buses
- GET /api/bus-route?route={route}&direction={inbound|outbound} — a route's ordered stops and road geometry
- GET /api/bus-live?route={route}&direction={inbound|outbound} — live vehicle positions for a route
- GET /api/line-route?lineId={id} — a rail line's ordered stops (trunk + branches)
- GET /api/line-status?lineId={id} — live status for one line, or the whole network if lineId is omitted (comma-separate for several)
- GET /api/station-search?q={query} — tube/rail station name lookup
- GET /api/lines — index of every rail line (id, name, kind); use to discover valid lineId values
- GET /api/routes — index of every active bus route (id, name); use to discover valid route values
- GET /api/health — liveness check; ?deep=1 also reports TfL upstream reachability
## Station lookup workflow
1. GET /api/station-search?q=Vauxhall to discover station ids.
2. GET /api/station-arrivals?id={id} using a returned id.
3. Check fetchedAt and stale before describing departures as current. If stale is true or fetchedAt is over 90 seconds old, disclose that updates are delayed. expectedArrival is an absolute timestamp; do not reuse old countdowns.
4. Refresh no faster than every 30 seconds for station boards. Treat 502 as temporary upstream failure, not an unknown station; only 404 means the station was not found.
## Notes
- Coordinates are WGS84 decimal lat/lon. Coverage is London and the TfL network catchment.
- Live endpoints are cached briefly server-side; route/line geometry is cached hard.
- Rail departures may include National Rail Enquiries data. Data © Transport for London. Map tiles © OpenStreetMap, © CARTO.
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |