LIRR 7050 Grand Central – Long Beach
Alerts for train 7050
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: Monday 16 November +4 min
Next service: today 15:52 from Grand Central · Tue 17 Nov
Last 30 days
Arrival delay at Long Beach, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 13 Nov Max en route +5 min · last fix heading to Lindenhurst +4 min
- Mon 16 Nov Max en route +6 min · last fix heading to Long Beach +4 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 6% · 1
- On time 83% · 15
- 3–10 min 11% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=2
- 100% W n=3
- 100% T n=4
- 75% F n=4
- 100% S n=1
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 15:52 | on time | on time | |
| 16:12 / 16:13 | ≈ on time | ≈ +1 min | |
| 16:19 | ≈ on time | ≈ +1 min | |
| 16:21 | ≈ on time | ≈ +2 min | |
| 16:24 | ≈ on time | ≈ +2 min | |
| 16:27 | ≈ on time | ≈ +2 min | |
| 16:30 | ≈ on time | ≈ +2 min | |
| 16:32 | ≈ on time | ≈ +2 min | |
| 16:34 | ≈ on time | ≈ +2 min | |
| 16:36 | ≈ on time | ≈ +2 min | |
| 16:40 | ≈ on time | ≈ +2 min | |
| 16:47 | on time | +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 |
|---|---|---|---|
| Mon 16 Nov | Long Beach 17:22 | +4 min | +6 min |
| Sun 15 Nov | Babylon 14:36 | −1 min | +3 min |
| Fri 13 Nov | Lindenhurst 00:27 | +4 min | +5 min |
| Thu 12 Nov | Huntington 20:54 | +1 min | +25 min |
| Wed 11 Nov | Long Beach 23:16 | +2 min | +11 min |
| Mon 5 Oct | — 06:18 | No data | — |
| Fri 2 Oct | — 17:11 | 0 min | — |
| Thu 1 Oct | — 19:07 | 0 min | — |
| Wed 30 Sept | — 19:59 | 0 min | — |
| Tue 29 Sept | — 19:59 | 0 min | — |
| Sun 30 Aug | — 21:38 | 0 min | — |
| Sat 29 Aug | — 19:59 | 0 min | — |
| Fri 28 Aug | — 17:41 | 0 min | — |
| Thu 27 Aug | — 19:59 | 0 min | — |
| Wed 26 Aug | — 19:59 | 0 min | — |
| Tue 25 Aug | — 21:26 | 0 min | — |
| Mon 24 Aug | — 19:59 | 0 min | — |
| Fri 21 Aug | — 02:17 | 0 min | — |
| Thu 20 Aug | — 19:59 | 0 min | — |