LIRR 7016 Babylon – Grand Central

View line LIRR

Babylon 05:13 → Grand Central 06:18 1 h 05 min · 10 stops MTA LIRR

Not running right now

Last recorded run: Friday 9 October −1 min

On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

Distribution · 90 days

30 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=6
  • 100% F n=7
  • 100% S n=3
  • 100% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 stops).

Last 90 days, 30 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.

StopSched.Usually 9 days in 10
05:13on time on time
05:19≈ on time ≈ on time
05:22≈ on time ≈ on time
05:24≈ on time ≈ on time
05:26≈ on time ≈ on time
05:28≈ on time ≈ on time
05:31≈ on time ≈ on time
05:34≈ on time ≈ on time
05:58 / 05:59≈ on time ≈ on time
06:18on time on time

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

DateLast stopFinalMax
Fri 9 OctGrand Central 06:57−1 min+4 min
Mon 5 Oct— 06:18No data—
Fri 2 Oct— 02:410 min—
Thu 1 Oct— 19:540 min—
Sun 27 Sept— 01:080 min—
Sat 26 Sept— 19:590 min—
Fri 25 Sept— 19:590 min—
Thu 24 Sept— 19:590 min—
Mon 21 Sept— 16:480 min—
Sun 20 Sept— 19:580 min—
Thu 17 Sept— 13:400 min—
Wed 16 Sept— 19:590 min—
Mon 14 Sept— 04:590 min—
Sat 12 Sept— 00:030 min—
Fri 11 Sept— 19:580 min—
Thu 10 Sept— 06:120 min—
Wed 9 Sept— 19:580 min—
Tue 8 Sept— 19:580 min—
Sat 5 Sept— 00:480 min—
Fri 4 Sept— 19:590 min—
Thu 3 Sept— 19:590 min—
Wed 2 Sept— 19:560 min—
Tue 1 Sept— 19:590 min—
Sun 30 Aug— 15:510 min—
Fri 28 Aug— 21:470 min—
Thu 27 Aug— 19:590 min—
Tue 25 Aug— 17:010 min—
Mon 24 Aug— 19:590 min—
Sun 23 Aug— 19:570 min—
Fri 21 Aug— 19:080 min—