Amtrak Cascades 511
View line Amtrak Cascades
Alerts for train 511
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Amtrak Cascades.
On-time · 30 days
25%
1/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
25%
1/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
Last 30 days
Delay at the end of each run, 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 5 Oct Max en route +58 min · last fix heading to Portland +51 min
- Tue 6 Oct Max en route +13 min · last fix heading to Kelso-Longview +12 min
- Sat 3 Oct Max en route +27 min · last fix heading to Portland +5 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 1
- On time 0% · 0
- 3–10 min 25% · 1
- 10–30 min 25% · 1
- 30+ min 25% · 1
On-time by weekday
- 0% M n=1
- 0% T n=1
- — W n=0
- — T n=0
- — F n=0
- 0% S n=1
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 6 Oct | Kelso-Longview 01:19 | +12 min | +13 min |
| Mon 5 Oct | Portland 03:23 | +51 min | +58 min |
| Sun 4 Oct | Portland 02:26 | −10 min | +16 min |
| Sat 3 Oct | Portland 02:40 | +5 min | +27 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.