LIRR 257 Babylon – Grand Central

View line LIRR

Babylon 15:18 → Grand Central 16:32 1 h 14 min · 17 stops Metro-North Railroad

Not running right now

Last recorded run: Friday 2 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
64%
21/33 runs under 3 min
RT coverage: 15 full · 18 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+4min
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

Worst days

  • Thu 3 Sept Max en route +8 min · last fix heading to 349 +7 min
  • Wed 2 Sept Max en route +7 min · last fix heading to 349 +6 min
  • Tue 18 Aug Max en route +8 min · last fix heading to 349 +4 min
  • Fri 18 Sept Max en route +6 min · last fix heading to 349 +4 min
  • Wed 19 Aug Max en route +8 min · last fix heading to 349 +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 64% · 21
  • 3–10 min 36% · 12
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 86% T n=7
  • 29% W n=7
  • 71% T n=7
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
15:18on time on time
15:24≈ on time ≈ on time
15:27≈ on time ≈ +1 min
15:29≈ on time ≈ +1 min
15:31≈ on time ≈ +1 min
15:33≈ on time ≈ +1 min
15:36≈ on time ≈ +1 min
15:39≈ on time ≈ +1 min
15:42≈ +1 min ≈ +2 min
15:45≈ +1 min ≈ +2 min
15:48≈ +1 min ≈ +2 min
15:51≈ +1 min ≈ +2 min
15:54≈ +1 min ≈ +3 min
15:57≈ +1 min ≈ +3 min
16:11 / 16:12≈ +1 min ≈ +4 min
16:17≈ +1 min ≈ +4 min
16:32+2 min +5 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

DateLast stopFinalMax
Fri 2 Oct349 17:12Partial coverage+1 min+4 min
Thu 1 Oct349 17:10Partial coverage+3 min+6 min
Wed 30 Sept349 17:11Partial coverage+3 min+6 min
Tue 29 Sept349 17:11Partial coverage+2 min+6 min
Mon 28 Sept349 17:11Partial coverage+1 min+4 min
Fri 25 Sept349 17:11Partial coverage+1 min+6 min
Thu 24 Sept349 17:11Partial coverage0 min+4 min
Wed 23 Sept349 17:11Partial coverage+1 min+3 min
Tue 22 Sept349 17:11Partial coverage+1 min+6 min
Mon 21 Sept349 17:10Partial coverage+1 min+6 min
Fri 18 Sept349 17:11Partial coverage+4 min+6 min
Thu 17 Sept349 17:11Partial coverage0 min+6 min
Wed 16 Sept349 17:11Partial coverage0 min+3 min
Tue 15 Sept349 17:11Partial coverage+2 min+6 min
Fri 11 Sept349 17:10Partial coverage+3 min+6 min
Thu 10 Sept349 17:12Partial coverage0 min+5 min
Wed 9 Sept349 17:12Partial coverage+3 min+8 min
Tue 8 Sept349 17:11Partial coverage+2 min+6 min
Fri 4 Sept349 17:110 min+4 min
Thu 3 Sept349 17:11+7 min+8 min
Wed 2 Sept349 17:11+6 min+7 min
Tue 1 Sept349 17:110 min+5 min
Mon 31 Aug349 17:11+3 min+6 min
Fri 28 Aug349 17:11+3 min+6 min
Thu 27 Aug349 17:11+1 min+4 min
Wed 26 Aug349 17:11+3 min+6 min
Tue 25 Aug349 17:11+1 min+4 min
Mon 24 Aug349 17:11+2 min+4 min
Fri 21 Aug349 17:11+2 min+6 min
Thu 20 Aug349 17:11+1 min+4 min