LIRR 6215 Massapequa – Grand Central
Alerts for train 6215
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: Saturday 3 October −2 min
Next service: Saturday 09:30 from Massapequa · Sat 14 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 15 Aug Max en route +10 min · last fix heading to 349 +5 min
Distribution · 90 days
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 57% · 8
- On time 36% · 5
- 3–10 min 7% · 1
- 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
- 86% S n=7
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 14 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 |
|---|---|---|---|
| 09:30 | on time | on time | |
| 09:33 | ≈ on time | ≈ on time | |
| 09:36 | ≈ on time | ≈ +1 min | |
| 09:39 | ≈ on time | ≈ +1 min | |
| 09:42 | ≈ on time | ≈ +1 min | |
| 09:45 | ≈ on time | ≈ +1 min | |
| 09:48 | ≈ 1 min early | ≈ +2 min | |
| 09:51 | ≈ 1 min early | ≈ +1 min | |
| 10:05 / 10:07 | ≈ 1 min early | ≈ +1 min | |
| 10:11 | ≈ 1 min early | ≈ +1 min | |
| 10:13 | ≈ 1 min early | ≈ +1 min | |
| 10:27 | 2 min early | +1 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 11:26Partial coverage | −2 min | +2 min |
| Sun 27 Sept | 349 11:27Partial coverage | +1 min | +4 min |
| Sat 26 Sept | 349 11:28Partial coverage | +2 min | +2 min |
| Sun 20 Sept | 349 11:06 | +1 min | +4 min |
| Sat 19 Sept | 349 11:05 | 0 min | +3 min |
| Mon 7 Sept | 349 11:07 | 0 min | +4 min |
| Sun 6 Sept | 349 11:07 | −3 min | +2 min |
| Sat 5 Sept | 349 11:06 | −2 min | +4 min |
| Sun 30 Aug | 349 11:05 | −2 min | +2 min |
| Sat 29 Aug | 349 11:05 | −2 min | +3 min |
| Sun 23 Aug | 349 11:17 | −3 min | +2 min |
| Sat 22 Aug | 349 11:17 | −5 min | +2 min |
| Sun 16 Aug | 349 11:16 | −6 min | +3 min |
| Sat 15 Aug | 349 11:16 | +5 min | +10 min |