LIRR 6195 Babylon – Penn Station

View line LIRR

Babylon 23:14 → Penn Station 00:17 Sat, Sun 1 h 03 min · 9 stops Metro-North Railroad

It has not run yet today

Last recorded run: Sunday 27 September −4 min

Next service: today 23:14 from Babylon · Sat 14 Nov

Next departure 23:14 today · Babylon
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
100%
11/11 runs under 3 min
RT coverage: 9 full · 2 partial · 0 no data
Typical delay
−2min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Penn Station, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 73% · 8
  • On time 27% · 3
  • 3–10 min 0% · 0
  • 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
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 11 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:14+1 min +1 min
23:20≈ +1 min ≈ +1 min
23:23≈ +1 min ≈ +1 min
23:25≈ +1 min ≈ +1 min
23:27≈ +1 min ≈ +1 min
23:29≈ on time ≈ +1 min
23:39≈ on time ≈ +1 min
23:57 / 23:59≈ 1 min early ≈ +1 min
00:172 min early +1 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 Sept237 01:05Partial coverage−4 min+2 min
Sat 26 Sept237 01:06Partial coverage−3 min+3 min
Sun 20 Sept237 01:01−3 min+2 min
Sat 19 Sept237 01:01+2 min+2 min
Mon 7 Sept237 01:01−1 min+2 min
Sun 6 Sept237 01:010 min+1 min
Sat 5 Sept237 01:00−2 min+1 min
Sun 30 Aug237 01:02−2 min—
Sat 29 Aug237 01:010 min+1 min
Sun 23 Aug237 01:00−3 min—
Sat 22 Aug237 01:00−3 min+1 min