LIRR 6180 Penn Station – Babylon

View line LIRR

Penn Station 19:21 → Babylon 20:30 Sat, Sun 1 h 09 min · 11 stops Metro-North Railroad

It does not run today

Last recorded run: Sunday 27 September +3 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
92%
12/13 runs under 3 min
RT coverage: 11 full · 2 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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

  • Sat 19 Sept Max en route +35 min · last fix heading to 27 +24 min

Distribution · 90 days

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

  • Early 8% · 1
  • On time 85% · 11
  • 3–10 min 0% · 0
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 83% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 13 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
19:21on time on time
19:37≈ on time ≈ +1 min
19:39≈ on time ≈ +1 min
19:43 / 19:45≈ on time ≈ +1 min
20:03≈ on time ≈ +2 min
20:13≈ on time ≈ +2 min
20:15≈ on time ≈ +2 min
20:18≈ on time ≈ +2 min
20:21≈ on time ≈ +2 min
20:24≈ on time ≈ +3 min
20:30on 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

DateLast stopFinalMax
Sun 27 Sept27 21:24Partial coverage+3 min+11 min
Sat 26 Sept27 21:27Partial coverage+1 min+7 min
Sun 20 Sept27 21:18+1 min+2 min
Sat 19 Sept27 23:09+24 min+35 min
Mon 7 Sept8 21:10+3 min+3 min
Sun 6 Sept27 21:10+2 min+4 min
Sat 5 Sept27 21:080 min+3 min
Sun 30 Aug27 21:11−1 min+2 min
Sat 29 Aug27 21:11−1 min+1 min
Sun 23 Aug27 21:17−2 min+2 min
Sat 22 Aug38 21:090 min+2 min
Sun 16 Aug8 21:110 min—
Sat 15 Aug27 21:100 min+4 min