414 STATIONS · 36 LINES · 4 NETWORKS
Every train, every fare, between any two stations.
LIRR, Metro-North, NJ Transit and PATH in one place. Built from the operators' own schedule feeds, updated weekly.
Networks
Popular trips
Look something up
How each network prices a ticket
Guides
How to read a trip page
A trip page is one direction between two stations, computed from the operator's own schedule feed on one representative weekday, Saturday and Sunday. The strip at the top gives the typical travel time, the one-way fare (two fares where the operator charges a peak price), the number of weekday trains and the distance.
The paragraph under it says which direction the page describes. That matters on the LIRR and Metro-North, where a peak fare is defined by arriving in Manhattan in the morning or leaving it in the evening, so the page for the return trip says something different about the same two prices.
Calling points are the stops on the all-stations run, each linked to its station page. Service gives first and last train, the typical gap and the fastest and slowest run. Stopping pattern tells you how many trains skip stops and how far apart trains are in the morning peak and at midday. Fares lists every ticket the operator publishes for the pair, and how many one-way rides a weekly or monthly ticket equals. The questions at the end are asked only where the data answers them.
Where the numbers come from
Every figure is computed from a feed or chart the operator publishes: the MTA's GTFS feeds for the LIRR and Metro-North, NJ Transit's rail feed, the PATH feed, and the operators' own fare charts and timetables. Nothing is estimated and nothing is copied from another website. Each page names its sources and the date they take effect.
Service counts are taken from one real service date in each bucket, chosen as the date the most trains run, so a "41 weekday trains" figure matches a day you could travel rather than an average across a month of timetable changes. A station's count is distinct trains, never a sum across platforms.
Before a page is written it is checked against sanity ranges for trains a day, travel time, fare and distance, and a page that fails is not published. Fares parsed from a PDF are tested against the operator's own price ratios, and a row that fails is dropped rather than corrected by guesswork. Where a fare is missing, the page shows no fare rather than a wrong one. Pages are released in stages, so every page you can reach here is one that has passed those checks. The full method is on the about page and the data sources page.