LIRR 188 Penn Station – Babylon

View line LIRR

Penn Station 21:31 → Babylon 22:32 Mon, Tue, Wed, Thu, Fri 1 h 01 min · 8 stops Metro-North Railroad

It has not run yet today

Last recorded run: Friday 2 October −1 min

Next service: today 21:31 from Penn Station · Wed 11 Nov

Next departure 21:31 today · Penn Station
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
91%
31/34 runs under 3 min
RT coverage: 16 full · 18 partial · 0 no data
Typical delay
−1min
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

  • Thu 1 Oct Max en route +11 min · last fix heading to 27 +10 min
  • Wed 30 Sept Max en route +11 min · last fix heading to 8 +7 min
  • Fri 25 Sept Max en route +4 min · last fix heading to 27 +4 min

Distribution · 90 days

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

  • Early 21% · 7
  • On time 71% · 24
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 86% W n=7
  • 86% T n=7
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
21:31on time +1 min
21:43≈ on time ≈ on time
21:51 / 21:53≈ on time ≈ on time
22:11≈ 1 min early ≈ on time
22:16≈ 1 min early ≈ on time
22:21≈ 1 min early ≈ on time
22:26≈ 1 min early ≈ on time
22:321 min early 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 2 Oct27 23:13Partial coverage−1 min+2 min
Thu 1 Oct27 23:23Partial coverage+10 min+11 min
Wed 30 Sept8 23:17Partial coverage+7 min+11 min
Tue 29 Sept27 23:16Partial coverage−1 min+2 min
Mon 28 Sept27 23:07Partial coverage−1 min—
Fri 25 Sept27 23:17Partial coverage+4 min+4 min
Thu 24 Sept27 23:15Partial coverage+3 min+3 min
Wed 23 Sept27 23:13Partial coverage0 min+1 min
Tue 22 Sept8 23:11Partial coverage−2 min—
Mon 21 Sept27 23:22Partial coverage−1 min—
Fri 18 Sept8 23:16Partial coverage0 min+2 min
Thu 17 Sept27 23:13Partial coverage−1 min—
Wed 16 Sept27 23:14Partial coverage−1 min+2 min
Tue 15 Sept27 23:14Partial coverage−1 min+2 min
Fri 11 Sept27 23:24Partial coverage+1 min+2 min
Thu 10 Sept27 23:15Partial coverage+3 min+9 min
Wed 9 Sept27 23:07Partial coverage0 min+1 min
Tue 8 Sept27 23:13Partial coverage0 min+4 min
Fri 4 Sept27 23:14−1 min—
Thu 3 Sept27 23:12−1 min+1 min
Wed 2 Sept27 23:15−1 min+2 min
Tue 1 Sept27 23:12−1 min—
Mon 31 Aug27 23:11−1 min—
Fri 28 Aug27 23:140 min+5 min
Thu 27 Aug27 23:140 min+1 min
Wed 26 Aug27 23:110 min—
Tue 25 Aug8 23:14−2 min+2 min
Mon 24 Aug27 23:11+1 min+4 min
Fri 21 Aug27 23:12−1 min—
Thu 20 Aug27 23:11−1 min+1 min