LIRR 7560 Penn Station – Huntington

View line LIRR

Penn Station 17:47 → Huntington 18:52 Sat, Sun 1 h 05 min · 11 stops MTA LIRR

It does not run today

Last recorded run: Monday 2 November +8 min

Next service: Saturday 17:47 from Penn Station · Sat 14 Nov

Next departure 17:47 Saturday · Penn Station
On-time · 30 days
56%
5/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 31 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +2 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Huntington, 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 2 Nov Max en route +9 min · last fix heading to Huntington +8 min
  • Thu 15 Oct Max en route +7 min · last fix heading to Amityville +6 min
  • Fri 16 Oct Max en route +6 min · last fix heading to Huntington +4 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Ronkonkoma +3 min

Distribution · 90 days

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

  • Early 35% · 11
  • On time 52% · 16
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=2
  • 100% W n=2
  • 50% T n=2
  • 50% F n=2
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 31 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
17:47on time +1 min
18:06 / 18:07≈ on time ≈ +1 min
18:18≈ on time ≈ +2 min
18:20≈ on time ≈ +2 min
18:23≈ on time ≈ +2 min
18:26≈ on time ≈ +2 min
18:29≈ on time ≈ +2 min
18:34≈ on time ≈ +2 min
18:40≈ on time ≈ +3 min
18:45≈ on time ≈ +3 min
18:52on time +3 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
Mon 2 NovHuntington 19:29+8 min+9 min
Mon 19 OctAmityville 02:12+1 min+1 min
Sun 18 OctMassapequa 22:42+2 min+2 min
Sat 17 OctRonkonkoma 00:070 min+14 min
Fri 16 OctHuntington 22:18+4 min+6 min
Thu 15 OctAmityville 21:49+6 min+7 min
Wed 14 OctBabylon 00:19−1 min+6 min
Tue 13 OctBabylon 21:16−4 min+4 min
Mon 12 OctRonkonkoma 01:34+3 min+3 min
Sun 11 OctPort Washington 00:23+3 min+5 min
Sat 10 OctBabylon 22:18−2 min+5 min
Fri 9 OctRonkonkoma 22:58−1 min+6 min
Thu 8 OctRonkonkoma 23:30−2 min+4 min
Wed 7 OctBabylon 21:15−1 min+4 min
Tue 6 OctRonkonkoma 01:34+3 min+3 min
Mon 5 OctRonkonkoma 21:22−1 min+11 min
Sun 4 Oct91 01:27+2 min+4 min
Sat 3 Oct91 16:160 min+2 min
Sun 27 Sept91 16:240 min+2 min
Sat 26 Sept91 16:19+3 min+4 min
Sun 20 Sept91 16:18−2 min—
Sat 19 Sept91 16:18+1 min+3 min
Mon 7 Sept91 16:22+1 min+3 min
Sun 6 Sept91 16:35−3 min+2 min
Sat 5 Sept91 16:17−1 min+2 min
Sun 30 Aug91 16:16−3 min+1 min
Sat 29 Aug91 16:16−1 min+2 min
Sun 23 Aug91 16:21+1 min+4 min
Sat 22 Aug91 16:210 min+7 min
Sun 16 Aug91 16:16−2 min+1 min