WTR 804 Penn Station – Long Beach

View line WTR

Penn Station 01:52 → Long Beach 02:42 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 11 stops SEPTA

It does not run today

Last recorded run: Friday 13 November +1 min

Next service: tomorrow 01:52 from Penn Station · Mon 16 Nov

Next departure 01:52 tomorrow · Penn Station
On-time · 30 days
50%
5/10 runs under 3 min
RT coverage: 9 full · 1 partial · 0 no data
On-time · 90 days
76%
32/42 runs under 3 min
RT coverage: 41 full · 1 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +3 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +12 min

Last 30 days

Arrival delay at Long Beach, in minutes. One bar per run.

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

Worst days

  • Tue 25 Aug Max en route +62 min · last fix heading to 113 +62 min
  • Sat 7 Nov Max en route +13 min · last fix heading to septa-rail:90225 +13 min
  • Fri 23 Oct Max en route +12 min · last fix heading to septa-rail:90531 +12 min
  • Wed 11 Nov Max en route +8 min · last fix heading to septa-rail:90417 +6 min
  • Tue 10 Nov Max en route +5 min · last fix heading to septa-rail:90417 +5 min

Distribution · 90 days

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

  • Early 7% · 3
  • On time 69% · 29
  • 3–10 min 17% · 7
  • 10–30 min 5% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=6
  • 50% T n=8
  • 88% W n=8
  • 88% T n=8
  • 70% F n=10
  • 0% S n=1
  • 100% S n=1

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
01:52on time +2 min
02:06≈ +1 min ≈ +3 min
02:08≈ +1 min ≈ +3 min
02:12 / 02:13≈ +1 min ≈ +3 min
02:22≈ +1 min ≈ +4 min
02:25≈ +1 min ≈ +4 min
02:27≈ +1 min ≈ +4 min
02:29≈ +1 min ≈ +4 min
02:31≈ +1 min ≈ +4 min
02:35≈ +1 min ≈ +4 min
02:42+1 min +5 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 13 Novsepta-rail:90327 15:40Partial coverage+1 min+5 min
Thu 12 Novsepta-rail:90417 17:25+4 min+4 min
Wed 11 Novsepta-rail:90417 17:27+6 min+8 min
Tue 10 Novsepta-rail:90417 17:27+5 min+5 min
Mon 9 Novsepta-rail:90007 19:570 min+13 min
Sun 8 Novsepta-rail:90007 00:040 min+10 min
Sat 7 Novsepta-rail:90225 22:53+13 min+13 min
Fri 6 Novsepta-rail:90411 00:09+2 min+53 min
Tue 27 Octsepta-rail:90327 20:340 min+19 min
Fri 23 Octsepta-rail:90531 18:05+12 min+12 min
Fri 9 Octsepta-rail:1 16:52No data—
Mon 5 Octsepta-rail:1 13:460 min+4 min
Fri 2 Oct113 03:16+5 min+7 min
Thu 1 Oct113 03:15+3 min+5 min
Wed 30 Sept113 03:120 min+17 min
Tue 29 Sept113 03:14+3 min+6 min
Mon 28 Sept113 03:12+1 min+3 min
Fri 25 Sept113 03:120 min+2 min
Thu 24 Sept113 03:14+3 min+4 min
Wed 23 Sept113 03:12+1 min+3 min
Tue 22 Sept113 03:120 min+2 min
Mon 21 Sept113 03:120 min+2 min
Fri 18 Sept113 03:11−1 min+1 min
Thu 17 Sept113 03:110 min+2 min
Wed 16 Sept113 03:110 min+2 min
Fri 11 Sept113 03:120 min+2 min
Thu 10 Sept113 03:13+2 min+4 min
Wed 9 Sept113 03:110 min+3 min
Tue 8 Sept113 03:11+1 min+4 min
Fri 4 Sept113 03:14+2 min+4 min