PAO 369 Port Washington – Penn Station

View line PAO

Port Washington 21:06 → Penn Station 21:55 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 14 stops SEPTA

It has not run yet today

Last recorded run: Thursday 29 October 0 min

Next service: tomorrow 21:06 from Port Washington · Tue 17 Nov

Next departure 21:06 tomorrow · Port Washington
On-time · 30 days
40%
2/5 runs under 3 min
RT coverage: 4 full · 1 partial · 0 no data
On-time · 90 days
74%
31/42 runs under 3 min
RT coverage: 41 full · 1 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +4 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +10 min

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

  • Thu 15 Oct Max en route +25 min · last fix heading to septa-rail:90715 +25 min
  • Mon 12 Oct Max en route +24 min · last fix heading to septa-rail:90413 +22 min
  • Mon 26 Oct Max en route +43 min · last fix heading to septa-rail:90005 +13 min
  • Tue 13 Oct Max en route +17 min · last fix heading to septa-rail:90006 +10 min
  • Fri 9 Oct Max en route +10 min · last fix heading to septa-rail:1 +8 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 71% · 30
  • 3–10 min 17% · 7
  • 10–30 min 10% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 88% T n=8
  • 71% W n=7
  • 73% T n=11
  • 67% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 42 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
21:06+3 min +6 min
21:12≈ +3 min ≈ +6 min
21:14≈ +3 min ≈ +5 min
21:17≈ +3 min ≈ +5 min
21:20≈ +2 min ≈ +6 min
21:22≈ +2 min ≈ +5 min
21:24≈ +2 min ≈ +5 min
21:27≈ +3 min ≈ +5 min
21:29≈ +3 min ≈ +5 min
21:31≈ +3 min ≈ +6 min
21:34≈ +2 min ≈ +6 min
21:36≈ +2 min ≈ +6 min
21:44≈ +2 min ≈ +7 min
21:55+2 min +8 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 29 Octsepta-rail:90501 19:36Partial coverage0 min+9 min
Mon 26 Octsepta-rail:90005 17:13+13 min+43 min
Fri 23 Octsepta-rail:90505 09:19+4 min+8 min
Thu 22 Octsepta-rail:1 22:490 min+12 min
Wed 21 Octsepta-rail:1 12:25+6 min+11 min
Thu 15 Octsepta-rail:90715 16:51+25 min+25 min
Tue 13 Octsepta-rail:90006 10:57+10 min+17 min
Mon 12 Octsepta-rail:90413 00:07+22 min+24 min
Fri 9 Octsepta-rail:1 23:54+8 min+10 min
Thu 8 Octsepta-rail:90505 00:540 min+10 min
Tue 6 Octsepta-rail:90505 17:070 min+4 min
Mon 5 Octsepta-rail:90505 20:070 min+8 min
Fri 2 Oct237 23:160 min+2 min
Thu 1 Oct237 23:170 min+4 min
Wed 30 Sept237 23:170 min+2 min
Tue 29 Sept237 23:16+2 min+4 min
Mon 28 Sept237 23:160 min+3 min
Fri 25 Sept237 23:15+1 min+5 min
Thu 24 Sept237 23:16−1 min+3 min
Wed 23 Sept237 22:500 min+3 min
Tue 22 Sept237 23:17+2 min+4 min
Mon 21 Sept237 23:16+2 min+3 min
Fri 18 Sept237 23:16+2 min+7 min
Thu 17 Sept237 23:16+6 min+10 min
Wed 16 Sept237 23:15+4 min+6 min
Tue 15 Sept237 23:15+1 min+5 min
Fri 11 Sept237 22:39+6 min+9 min
Thu 10 Sept237 22:450 min+5 min
Wed 9 Sept237 22:40+2 min+6 min
Tue 8 Sept237 23:16+1 min+3 min