LIRR 6054 Babylon – Speonk

View line LIRR

Babylon 11:35 → Speonk 12:35 Sat, Sun 1 h 00 min · 10 stops Metro-North Railroad

It does not run today

Last recorded run: Saturday 3 October +1 min

Next service: Sunday 11:35 from Babylon · Sun 15 Nov

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

Last 30 days

Arrival delay at Speonk, in minutes. One bar per run.

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

Worst days

  • Sun 6 Sept Max en route +9 min · last fix heading to 198 +4 min

Distribution · 90 days

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

  • Early 64% · 9
  • On time 29% · 4
  • 3–10 min 7% · 1
  • 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=7
  • 83% S n=6

Stops and timetable

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

Last 90 days, 14 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
11:35+2 min +4 min
11:41≈ +2 min ≈ +3 min
11:46≈ +2 min ≈ +3 min
11:49≈ +1 min ≈ +2 min
11:53≈ +1 min ≈ +2 min
11:58≈ +1 min ≈ +2 min
12:05≈ on time ≈ +1 min
12:12≈ on time ≈ +1 min
12:19≈ on time ≈ +1 min
12:351 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
Sat 3 Oct198 13:13Partial coverage+1 min+4 min
Sun 27 Sept198 13:13Partial coverage−1 min+5 min
Sat 26 Sept198 13:13Partial coverage−1 min+5 min
Sun 20 Sept198 13:040 min+3 min
Sat 19 Sept198 13:04−3 min+3 min
Mon 7 Sept198 13:04−3 min+3 min
Sun 6 Sept198 13:08+4 min+9 min
Sat 5 Sept198 13:05+1 min+6 min
Sun 30 Aug198 13:01−3 min+1 min
Sat 29 Aug198 13:04−1 min+5 min
Sun 23 Aug198 13:03−4 min+2 min
Sat 22 Aug198 13:03−1 min+3 min
Sun 16 Aug198 13:04−1 min+3 min
Sat 15 Aug198 13:04−4 min+3 min