LIRR 6198 Penn Station – Babylon

View line LIRR

Penn Station 23:43 → Babylon 00:59 Sat, Sun 1 h 16 min · 17 stops Metro-North Railroad

It does not run today

Last recorded run: Sunday 27 September +4 min

Next service: Saturday 23:43 from Penn Station · Sat 14 Nov

Next departure 23:43 Saturday · 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
77%
10/13 runs under 3 min
RT coverage: 9 full · 4 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 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 26 Sept Max en route +6 min · last fix heading to 8 +5 min
  • Sun 27 Sept Max en route +5 min · last fix heading to 27 +4 min
  • Sun 6 Sept Max en route +4 min · last fix heading to 8 +3 min

Distribution · 90 days

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

  • Early 15% · 2
  • On time 62% · 8
  • 3–10 min 23% · 3
  • 10–30 min 0% · 0
  • 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
  • 67% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (17 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
23:43on time on time
23:54≈ on time ≈ +1 min
00:04 / 00:06≈ on time ≈ +1 min
00:20≈ +1 min ≈ +1 min
00:22≈ +1 min ≈ +1 min
00:25≈ +1 min ≈ +1 min
00:28≈ +1 min ≈ +1 min
00:31≈ +1 min ≈ +2 min
00:34≈ +1 min ≈ +2 min
00:37≈ +1 min ≈ +2 min
00:40≈ +1 min ≈ +2 min
00:42≈ +1 min ≈ +2 min
00:44≈ +1 min ≈ +2 min
00:47≈ +1 min ≈ +2 min
00:50≈ +1 min ≈ +2 min
00:53≈ +1 min ≈ +2 min
00:59+2 min +2 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 01:36Partial coverage+4 min+5 min
Sat 26 Sept8 01:42Partial coverage+5 min+6 min
Sun 20 Sept27 01:43Partial coverage−1 min+2 min
Sat 19 Sept27 01:39Partial coverage0 min+3 min
Mon 7 Sept27 01:40−3 min—
Sun 6 Sept8 01:40+3 min+4 min
Sat 5 Sept8 01:38+2 min+5 min
Sun 30 Aug27 01:42+2 min+5 min
Sat 29 Aug27 01:43+2 min+4 min
Sun 23 Aug27 01:42+2 min+5 min
Sat 22 Aug8 01:33+1 min+2 min
Sun 16 Aug27 01:390 min+4 min
Sat 15 Aug27 01:42−1 min+2 min