LIRR 7108 Grand Central – Babylon

View line LIRR

Grand Central 13:56 → Babylon 15:12 Mon, Tue, Wed, Fri, Sun 1 h 16 min · 18 stops MTA LIRR

It does not run today

Last recorded run: Friday 6 November 0 min

On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Babylon, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 19 Oct Max en route +7 min · last fix heading to Huntington +5 min

Distribution · 90 days

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

  • Early 7% · 3
  • On time 90% · 38
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 100% W n=7
  • 100% T n=5
  • 100% F n=8
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

Last 90 days, 42 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
13:56on time on time
14:11≈ on time ≈ +1 min
14:13≈ on time ≈ +1 min
14:17 / 14:19≈ on time ≈ +1 min
14:32≈ on time ≈ on time
14:35≈ on time ≈ on time
14:38≈ on time ≈ on time
14:41≈ on time ≈ on time
14:44≈ on time ≈ on time
14:47≈ on time ≈ on time
14:50≈ on time ≈ on time
14:53≈ on time ≈ on time
14:55≈ on time ≈ on time
14:57≈ on time ≈ on time
15:00≈ on time ≈ on time
15:03≈ on time ≈ on time
15:06≈ on time ≈ on time
15:12on 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 6 NovBabylon 15:570 min+1 min
Wed 4 NovElmont-UBS Arena 12:380 min+2 min
Tue 3 NovRonkonkoma 21:56−1 min+3 min
Mon 19 OctHuntington 19:26+5 min+7 min
Sun 18 OctHuntington 00:07−1 min—
Fri 16 OctRonkonkoma 22:59+1 min+3 min
Mon 5 Oct— 06:18No data—
Sun 4 Oct65 14:14−2 min+3 min
Fri 2 Oct— 17:110 min—
Thu 1 Oct— 19:580 min—
Wed 30 Sept— 19:590 min—
Tue 29 Sept— 19:590 min—
Mon 28 Sept— 19:590 min—
Sun 27 Sept— 19:590 min—
Fri 25 Sept— 01:070 min—
Wed 23 Sept— 21:080 min—
Tue 22 Sept— 19:590 min—
Mon 21 Sept— 19:590 min—
Sun 20 Sept— 19:580 min—
Fri 18 Sept— 01:440 min—
Wed 16 Sept— 01:450 min—
Tue 15 Sept— 19:590 min—
Mon 14 Sept— 19:590 min—
Sat 12 Sept— 01:220 min—
Fri 11 Sept— 19:580 min—
Thu 10 Sept— 19:580 min—
Wed 9 Sept— 19:580 min—
Tue 8 Sept— 19:580 min—
Sun 6 Sept— 21:040 min—
Sat 5 Sept— 19:590 min—