App Logo
thetrainline.com

Search train journeys (+ all stops)

Search train journeys between two cities/stations on a date via Trainline: departure/arrival times, duration, changes, legs (train number, carrier). With includeStops=true, also returns every calling point of each train (all stops with scheduled times, platform, realtime status when available).

Input

to required

Destination city or station, free text

date required

Outbound date 'YYYY-MM-DD' (defaults to 08:00) or 'YYYY-MM-DDTHH:mm' — journeys departing after this time

from required

Origin city or station, free text (e.g. 'Paris', 'Lyon Part-Dieu', 'London')

max optional

Max journeys returned (no pagination fan-out; the site returns ~8 per search). Default 10.

includeStops optional

If true, fetch all calling points (every stop of the full train route, incl. before/after the searched segment) for each leg. Default false.

Output

origin required

Resolved origin (first autocomplete match)

journeys required
destination required

Resolved destination

FAQ

Search train journeys between two cities/stations on a date via Trainline: departure/arrival times, duration, changes, legs (train number, carrier). With includeStops=true, also returns every calling point of each train (all stops with scheduled times, platform, realtime status when available).
Required: from, to, date. Optional: max, includeStops.
It returns origin, journeys, destination.
No. It only uses pages of thetrainline.com that are reachable without signing in.
It only reads. It looks things up on thetrainline.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/thetrainline.com/search_journeys, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/thetrainline.com/search_journeys
It is part of Reduck's official curated catalogue.

Start building not clicking

Get started for free