LIRR 36 Babylon – Speonk

View line LIRR

Babylon 11:31 → Speonk 12:31 Mon, Tue, Wed, Thu, Fri 1 h 00 min · 10 stops Metro-North Railroad

It does not run today

Last recorded run: Friday 2 October −1 min

Next service: tomorrow 11:31 from Babylon · Mon 9 Nov

Next departure 11:31 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
89%
33/37 runs under 3 min
RT coverage: 19 full · 18 partial · 0 no data
Typical delay
−3min
Median at arrival, 90 days
P90
+2min
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

  • Mon 31 Aug Max en route +31 min · last fix heading to 198 +26 min
  • Thu 3 Sept Max en route +20 min · last fix heading to 198 +10 min
  • Thu 27 Aug Max en route +14 min · last fix heading to 198 +6 min
  • Wed 23 Sept Max en route +13 min · last fix heading to 198 +5 min

Distribution · 90 days

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

  • Early 81% · 30
  • On time 8% · 3
  • 3–10 min 5% · 2
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=8
  • 88% W n=8
  • 75% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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:31+2 min +5 min
11:37≈ +3 min ≈ +5 min
11:42≈ +3 min ≈ +5 min
11:45≈ +2 min ≈ +5 min
11:49≈ +2 min ≈ +5 min
11:54≈ +1 min ≈ +6 min
12:01≈ on time ≈ +6 min
12:08≈ 1 min early ≈ +6 min
12:15≈ 1 min early ≈ +7 min
12:313 min early +7 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
Fri 2 Oct198 13:00Partial coverage−1 min+4 min
Thu 1 Oct198 13:03Partial coverage−3 min+3 min
Wed 30 Sept198 13:00Partial coverage−3 min+3 min
Tue 29 Sept198 13:01Partial coverage0 min+6 min
Mon 28 Sept198 13:00Partial coverage−4 min+2 min
Fri 25 Sept198 13:00Partial coverage−5 min+1 min
Thu 24 Sept198 12:59Partial coverage−5 min+3 min
Wed 23 Sept198 13:06Partial coverage+5 min+13 min
Tue 22 Sept198 13:00Partial coverage−5 min+3 min
Mon 21 Sept198 13:00Partial coverage−3 min+5 min
Fri 18 Sept198 12:59Partial coverage−5 min+2 min
Thu 17 Sept198 13:01Partial coverage−5 min+3 min
Wed 16 Sept198 13:00Partial coverage−6 min+1 min
Tue 15 Sept198 13:00Partial coverage−7 min+1 min
Fri 11 Sept198 13:00Partial coverage−5 min+4 min
Thu 10 Sept198 13:00Partial coverage−2 min+2 min
Wed 9 Sept198 13:00Partial coverage−7 min+1 min
Tue 8 Sept198 12:59Partial coverage−3 min+3 min
Fri 4 Sept198 13:01−6 min+2 min
Thu 3 Sept198 13:12+10 min+20 min
Wed 2 Sept198 13:00−6 min+4 min
Tue 1 Sept198 13:00−5 min+4 min
Mon 31 Aug198 13:26+26 min+31 min
Fri 28 Aug198 12:59−4 min+3 min
Thu 27 Aug198 13:07+6 min+14 min
Wed 26 Aug198 13:01−3 min+4 min
Tue 25 Aug198 13:01−7 min+1 min
Mon 24 Aug198 13:000 min+6 min
Fri 21 Aug198 13:000 min+5 min
Thu 20 Aug198 13:00−3 min+5 min