LIRR 418 Babylon – Patchogue

View line LIRR

Babylon 22:36 → Patchogue 23:06 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 7 stops MTA LIRR

It has not run yet today

Last recorded run: Thursday 12 November +5 min

Next service: today 22:36 from Babylon · Fri 13 Nov

Next departure 22:36 today · Babylon
On-time · 30 days
54%
15/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
67%
44/66 runs under 3 min
RT coverage: 66 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +3 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +7 min

Last 30 days

Arrival delay at Patchogue, 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 7 Nov Max en route +27 min · last fix heading to Port Jefferson +27 min
  • Mon 5 Oct Max en route +23 min · last fix heading to Port Jefferson +22 min
  • Sun 1 Nov Max en route +22 min · last fix heading to Port Jefferson +20 min
  • Fri 23 Oct Max en route +15 min · last fix heading to Patchogue +10 min
  • Sat 24 Oct Max en route +6 min · last fix heading to Patchogue +6 min

Distribution · 90 days

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

  • Early 11% · 7
  • On time 56% · 37
  • 3–10 min 29% · 19
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 73% M n=11
  • 45% T n=11
  • 77% W n=13
  • 75% T n=12
  • 80% F n=10
  • 40% S n=5
  • 50% S n=4

Stops and timetable

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

Last 90 days, 66 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
22:36+1 min +6 min
22:42≈ +1 min ≈ +6 min
22:47≈ +2 min ≈ +5 min
22:50≈ +2 min ≈ +5 min
22:54≈ +2 min ≈ +5 min
22:59≈ +2 min ≈ +5 min
23:06+2 min +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
Thu 12 NovPatchogue 23:42+5 min+55 min
Wed 11 NovPatchogue 23:40+3 min+4 min
Tue 10 NovPort Jefferson 23:430 min+13 min
Mon 9 Nov— 12:12−3 min+4 min
Sun 8 NovPort Jefferson 01:08+5 min+19 min
Sat 7 NovPort Jefferson 01:43+27 min+27 min
Fri 6 NovPort Jefferson 22:43+3 min+8 min
Thu 5 Nov— 12:14−1 min+5 min
Wed 4 Nov— 12:20+6 min+12 min
Tue 3 NovMontauk 21:56−5 min+7 min
Mon 2 NovPatchogue 23:41+3 min+6 min
Sun 1 NovPort Jefferson 23:30+20 min+22 min
Sat 31 OctPort Jefferson 23:15+5 min+8 min
Fri 30 OctPatchogue 23:39+2 min+13 min
Thu 29 OctSpeonk 22:08+4 min+8 min
Wed 28 OctSpeonk 18:45−4 min+6 min
Tue 27 OctOyster Bay 01:07−3 min+6 min
Mon 26 OctOyster Bay 00:42+3 min+7 min
Sat 24 OctPatchogue 17:51+6 min+6 min
Fri 23 OctPatchogue 23:44+10 min+15 min
Thu 22 OctJamaica 00:59−3 min+13 min
Wed 21 OctPort Jefferson 22:46+3 min+7 min
Tue 20 OctPort Jefferson 21:00+5 min+7 min
Mon 19 OctSpeonk 01:040 min+8 min
Sun 18 OctOyster Bay 16:14+3 min+6 min
Sat 17 OctSpeonk 01:46−5 min+15 min
Fri 16 OctSpeonk 22:05+1 min+6 min
Thu 15 OctSpeonk 18:45−2 min+7 min
Wed 14 Octsepta-rail:90007 23:530 min+7 min
Mon 12 Octsepta-rail:90007 23:530 min+7 min