LIRR 6255 Babylon → Grand Central
Alerts for train 6255
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.
Train 6255 Babylon–Grand Central: final delay under 3 min on 8 of its 10 runs with data in the last 90 days (80%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 15:07 (GMT-5).
An alert on this phone or computer when the 6255 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 3 October +3 min
Next service: Thursday 14:38 from Babylon · Thu 26 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
- Sat 19 Sept Max en route +5 min · last fix heading to 349 +5 min
- Sat 3 Oct Max en route +4 min · last fix heading to 349 +3 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 30% · 3
- On time 50% · 5
- 3–10 min 20% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 60% S n=5
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (16 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 14:38 | on time | +1 min | |
| 14:44 | ≈ on time | ≈ +1 min | |
| 14:47 | ≈ on time | ≈ +1 min | |
| 14:49 | ≈ on time | ≈ +1 min | |
| 14:51 | ≈ on time | ≈ +1 min | |
| 14:53 | ≈ on time | ≈ +1 min | |
| 14:56 | ≈ on time | ≈ +1 min | |
| 14:59 | ≈ on time | ≈ +1 min | |
| 15:02 | ≈ on time | ≈ +1 min | |
| 15:05 | ≈ on time | ≈ +1 min | |
| 15:08 | ≈ on time | ≈ +1 min | |
| 15:11 | ≈ on time | ≈ +1 min | |
| 15:14 | ≈ on time | ≈ +2 min | |
| 15:16 | ≈ on time | ≈ +2 min | |
| 15:29 / 15:31 | ≈ on time | ≈ +2 min | |
| 15:51 | 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 |
|---|---|---|---|
| Sat 3 Oct | 349 16:27Partial coverage | +3 min | +4 min |
| Sun 27 Sept | 349 16:27Partial coverage | −3 min | +2 min |
| Sat 26 Sept | 349 16:28Partial coverage | +1 min | +9 min |
| Sun 20 Sept | 349 16:06 | +2 min | +2 min |
| Sat 19 Sept | 349 16:06 | +5 min | +5 min |
| Mon 7 Sept | 349 16:07 | 0 min | +2 min |
| Sun 6 Sept | 349 16:07 | −1 min | +3 min |
| Sat 5 Sept | 349 16:06 | −2 min | +2 min |
| Sun 30 Aug | 349 16:06 | −2 min | +2 min |
| Sat 29 Aug | 349 16:05 | −1 min | +3 min |