LIRR 6105 Babylon – Penn Station

View line LIRR

Babylon 01:40 → Penn Station 02:52 Sat, Sun 1 h 12 min · 18 stops Metro-North Railroad

It does not run today

Last recorded run: Saturday 3 October −1 min

Next service: tomorrow 01:40 from Babylon · Sat 14 Nov

Next departure 01:40 tomorrow · 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
85%
11/13 runs under 3 min
RT coverage: 10 full · 3 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
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

Worst days

  • Mon 7 Sept Max en route +9 min · last fix heading to 237 +8 min
  • Sun 30 Aug Max en route +6 min · last fix heading to 237 +4 min

Distribution · 90 days

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

  • Early 31% · 4
  • On time 54% · 7
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (18 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
01:40on time on time
01:46≈ on time ≈ +1 min
01:49≈ on time ≈ +1 min
01:51≈ on time ≈ +2 min
01:53≈ on time ≈ +2 min
01:55≈ on time ≈ +2 min
01:58≈ on time ≈ +2 min
02:01≈ on time ≈ +2 min
02:04≈ on time ≈ +3 min
02:07≈ on time ≈ +3 min
02:10≈ on time ≈ +2 min
02:13≈ on time ≈ +2 min
02:16≈ on time ≈ +2 min
02:19≈ on time ≈ +3 min
02:32 / 02:33≈ on time ≈ +3 min
02:37≈ on time ≈ +4 min
02:39≈ on time ≈ +4 min
02:52on time +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
Sat 3 Oct237 04:05Partial coverage−1 min+4 min
Sun 27 Sept237 04:04Partial coverage−1 min+4 min
Sat 26 Sept237 04:06Partial coverage0 min+4 min
Sun 20 Sept237 03:36+1 min+3 min
Sat 19 Sept237 03:350 min+9 min
Mon 7 Sept237 03:37+8 min+9 min
Sun 6 Sept237 03:36−1 min+3 min
Sat 5 Sept237 03:360 min+8 min
Sun 30 Aug237 03:37+4 min+6 min
Sat 29 Aug237 03:35+1 min+5 min
Sun 23 Aug237 03:36+2 min+5 min
Sat 22 Aug237 03:36−2 min+5 min
Sun 16 Aug237 03:36−3 min+3 min