LIRR 275 Babylon – Grand Central
Alerts for train 275
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line LIRR.
It has not run yet today
Last recorded run: Friday 2 October −5 min
Next service: today 23:17 from Babylon · Thu 12 Nov
Last 30 days
Arrival delay at Grand Central, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 9 Sept Max en route +5 min · last fix heading to 349 +5 min
- Thu 17 Sept Max en route +4 min · last fix heading to 349 +4 min
- Thu 10 Sept Max en route +3 min · last fix heading to 349 +3 min
- Wed 2 Sept Max en route +3 min · last fix heading to 349 +3 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 47% · 15
- On time 41% · 13
- 3–10 min 13% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=7
- 71% W n=7
- 71% T n=7
- 100% F n=6
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 32 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 23:17 | +1 min | +2 min | |
| 23:23 | ≈ +1 min | ≈ +2 min | |
| 23:26 | ≈ +1 min | ≈ +2 min | |
| 23:28 | ≈ +1 min | ≈ +2 min | |
| 23:30 | ≈ +1 min | ≈ +2 min | |
| 23:32 | ≈ +1 min | ≈ +2 min | |
| 23:35 | ≈ +1 min | ≈ +2 min | |
| 23:38 | ≈ +1 min | ≈ +2 min | |
| 23:41 | ≈ +1 min | ≈ +2 min | |
| 23:44 | ≈ +1 min | ≈ +2 min | |
| 23:47 | ≈ +1 min | ≈ +2 min | |
| 23:50 | ≈ +1 min | ≈ +2 min | |
| 23:53 | ≈ +1 min | ≈ +2 min | |
| 23:56 | ≈ +1 min | ≈ +2 min | |
| 00:10 / 00:12 | ≈ on time | ≈ +3 min | |
| 00:21 | ≈ on time | ≈ +3 min | |
| 00:32 | 1 min early | +3 min |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 10 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 2 Oct | 349 01:12Partial coverage | −5 min | — |
| Thu 1 Oct | 349 01:11 | +3 min | +3 min |
| Wed 30 Sept | 349 01:12 | +2 min | +2 min |
| Tue 29 Sept | 349 01:12 | −2 min | — |
| Mon 28 Sept | 349 01:11 | −1 min | +2 min |
| Fri 25 Sept | 349 01:18Partial coverage | 0 min | +7 min |
| Thu 24 Sept | 349 01:12 | +1 min | +2 min |
| Wed 23 Sept | 349 01:11 | +2 min | +3 min |
| Tue 22 Sept | 349 01:11 | −2 min | +3 min |
| Mon 21 Sept | 349 01:10 | −2 min | +2 min |
| Fri 18 Sept | 349 01:11 | −1 min | +1 min |
| Thu 17 Sept | 349 01:11 | +4 min | +4 min |
| Wed 16 Sept | 349 01:11 | +2 min | +3 min |
| Tue 15 Sept | 349 01:11 | −1 min | +2 min |
| Thu 10 Sept | 349 01:10 | +3 min | +3 min |
| Wed 9 Sept | 349 01:12 | +5 min | +5 min |
| Tue 8 Sept | 349 01:11 | 0 min | +1 min |
| Fri 4 Sept | 349 01:11 | +2 min | +2 min |
| Thu 3 Sept | 349 01:11 | +2 min | +3 min |
| Wed 2 Sept | 349 01:11 | +3 min | +3 min |
| Tue 1 Sept | 349 01:11 | −2 min | — |
| Mon 31 Aug | 349 01:11 | −1 min | +1 min |
| Fri 28 Aug | 349 01:11 | +1 min | +2 min |
| Thu 27 Aug | 349 01:11 | −1 min | +1 min |
| Wed 26 Aug | 349 01:11 | −3 min | +2 min |
| Tue 25 Aug | 349 01:11 | −4 min | +3 min |
| Mon 24 Aug | 349 01:11 | −2 min | +3 min |
| Fri 21 Aug | 349 01:11 | −4 min | +1 min |
| Thu 20 Aug | 349 01:11 | 0 min | +2 min |
| Wed 19 Aug | 349 01:11 | −2 min | — |