LIRR 7050 Penn Station – Huntington

View line LIRR

Penn Station 06:09 → Huntington 07:19 Mon, Tue, Wed, Thu, Fri 1 h 10 min · 13 stops MTA LIRR

✓ Today’s run finished

Today it reached Huntington at 07:19 −1 min

  1. Penn Station06:09
  2. Hillside Facility06:34
  3. New Hyde Park06:43
  4. Mineola06:48
  5. Westbury06:54
  6. Syosset07:06
  7. Huntington07:19

Next service: tomorrow 06:09 from Penn Station · Tue 17 Nov

Next departure 06:09 tomorrow · Penn Station
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Lindenhurst +4 min

Distribution · 90 days

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

  • Early 5% · 1
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 100% S n=1
  • 100% S n=2

Stops and timetable

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

Last 90 days, 19 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
06:09on time on time
06:29 / 06:30≈ on time ≈ on time
06:34≈ on time ≈ on time
06:41≈ on time ≈ +1 min
06:43≈ on time ≈ +1 min
06:45≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:51≈ on time ≈ +1 min
06:54≈ on time ≈ +1 min
06:59≈ on time ≈ +1 min
07:06≈ on time ≈ +1 min
07:11≈ on time ≈ +1 min
07:19on time +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
Mon 16 NovHuntington 07:49−1 min+3 min
Sun 15 NovBabylon 14:36−1 min+3 min
Fri 13 NovLindenhurst 00:27+4 min+5 min
Thu 12 NovHuntington 20:54+1 min+25 min
Wed 11 NovLong Beach 23:16+2 min+11 min
Mon 5 Oct— 06:18No data—
Fri 2 Oct— 17:110 min—
Thu 1 Oct— 19:070 min—
Wed 30 Sept— 19:590 min—
Tue 29 Sept— 19:590 min—
Sun 30 Aug— 21:380 min—
Sat 29 Aug— 19:590 min—
Fri 28 Aug— 17:410 min—
Thu 27 Aug— 19:590 min—
Wed 26 Aug— 19:590 min—
Tue 25 Aug— 21:260 min—
Mon 24 Aug— 19:590 min—
Fri 21 Aug— 02:170 min—
Thu 20 Aug— 19:590 min—
Wed 19 Aug— 19:590 min—