LAN 303 Great Neck – Penn Station

View line LAN

Great Neck 00:48 → Penn Station 01:25 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 11 stops SEPTA

It has not run yet today

Last recorded run: Thursday 5 November +5 min

Next service: Monday 00:48 from Great Neck · Mon 9 Nov

Next departure 00:48 Monday · Great Neck
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 1 full · 1 partial · 0 no data
On-time · 90 days
90%
35/39 runs under 3 min
RT coverage: 38 full · 1 partial · 0 no data
Typical delay
−3min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Penn Station, in minutes. One bar per run.

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

Worst days

  • Wed 16 Sept Max en route +21 min · last fix heading to 237 +19 min
  • Wed 4 Nov Max en route +25 min · last fix heading to septa-rail:90007 +15 min
  • Thu 5 Nov Max en route +8 min · last fix heading to septa-rail:90538 +5 min
  • Wed 9 Sept Max en route +7 min · last fix heading to 237 +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 67% W n=9
  • 89% T n=9
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
00:48+1 min +3 min
00:51≈ +1 min ≈ +2 min
00:53≈ +1 min ≈ +2 min
00:55≈ +1 min ≈ +3 min
00:58≈ on time ≈ +2 min
01:00≈ on time ≈ +2 min
01:02≈ on time ≈ +2 min
01:04≈ on time ≈ +2 min
01:06≈ 1 min early ≈ +2 min
01:14≈ 2 min early ≈ +2 min
01:253 min early +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
Thu 5 Novsepta-rail:90538 18:07Partial coverage+5 min+8 min
Wed 4 Novsepta-rail:90007 00:13+15 min+25 min
Fri 2 Oct237 02:08−5 min—
Thu 1 Oct237 02:09−1 min+4 min
Wed 30 Sept237 02:09−1 min+2 min
Tue 29 Sept237 02:10−4 min—
Mon 28 Sept237 02:09−4 min+2 min
Fri 25 Sept237 02:09−3 min+1 min
Thu 24 Sept237 02:10−2 min—
Wed 23 Sept237 02:09−4 min—
Tue 22 Sept237 02:09−2 min+1 min
Mon 21 Sept237 02:22+1 min+1 min
Fri 18 Sept237 02:10−2 min—
Thu 17 Sept237 02:09−3 min—
Wed 16 Sept237 02:42+19 min+21 min
Fri 11 Sept237 02:09+3 min+3 min
Thu 10 Sept237 02:09−3 min+2 min
Wed 9 Sept237 02:08+3 min+7 min
Tue 8 Sept237 02:10+1 min+6 min
Fri 4 Sept237 02:090 min+2 min
Thu 3 Sept237 02:09−5 min+2 min
Wed 2 Sept237 02:09−3 min+1 min
Tue 1 Sept237 02:09+1 min+4 min
Mon 31 Aug237 02:09+3 min+6 min
Fri 28 Aug237 02:08−2 min+2 min
Thu 27 Aug237 02:10−4 min+2 min
Wed 26 Aug237 03:140 min+2 min
Tue 25 Aug237 02:09−3 min+3 min
Mon 24 Aug237 02:26−5 min+2 min
Fri 21 Aug237 02:09−5 min+3 min