Acela 2249 Boston – Washington Union Station
Alerts for train 2249
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Acela.
✓ Today’s run finished
Today it reached Washington Union Station at 13:11 0 min
- Boston06:05
- Route 128 Amtrak Station06:18
- New Haven08:08
- Newark10:19
- Philadelphia11:17
- Baltimore Penn Station12:25
- Washington Union Station13:11
Next service: tomorrow 06:05 from Boston · Sun 8 Nov
Last 30 days
Arrival delay at Washington Union 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
- Sat 24 Oct Max en route +36 min · last fix heading to Washington Union Station +16 min
- Sat 17 Oct Max en route +26 min · last fix heading to Washington Union Station +15 min
- Sun 1 Nov Max en route +15 min · last fix heading to Washington Union Station +11 min
- Sun 25 Oct Max en route +12 min · last fix heading to Washington Union Station +9 min
- Sat 31 Oct Max en route +15 min · last fix heading to Washington Union Station +5 min
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 13% · 1
- On time 25% · 2
- 3–10 min 25% · 2
- 10–30 min 38% · 3
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 25% S n=4
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 8 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:05 | on time | +10 min | |
| 06:09 / 06:10 | ≈ on time | ≈ +10 min | |
| 06:18 / 06:20 | ≈ on time | ≈ +10 min | |
| 06:39 / 06:41 | ≈ +1 min | ≈ +10 min | |
| 08:08 / 08:10 | ≈ +3 min | ≈ +10 min | |
| 08:53 / 08:55 | ≈ +4 min | ≈ +11 min | |
| 09:53 / 10:03 | ≈ +4 min | ≈ +12 min | |
| 10:19 / 10:20 | ≈ +5 min | ≈ +12 min | |
| 10:32 / 10:34 | ≈ +5 min | ≈ +12 min | |
| 11:17 / 11:19 | ≈ +6 min | ≈ +13 min | |
| 11:38 / 11:40 | ≈ +6 min | ≈ +14 min | |
| 12:25 / 12:27 | ≈ +6 min | ≈ +14 min | |
| 12:38 / 12:40 | ≈ +7 min | ≈ +15 min | |
| 13:11 | +7 min | +15 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Washington Union Station 13:27 | 0 min | +15 min |
| Sun 1 Nov | Washington Union Station 13:36 | +11 min | +15 min |
| Sat 31 Oct | Washington Union Station 13:33 | +5 min | +15 min |
| Sun 25 Oct | Washington Union Station 13:54 | +9 min | +12 min |
| Sat 24 Oct | Washington Union Station 14:06 | +16 min | +36 min |
| Sun 18 Oct | Washington Union Station 13:47 | 0 min | +6 min |
| Sat 17 Oct | Washington Union Station 13:59 | +15 min | +26 min |
| Sun 11 Oct | Washington Union Station 13:23 | −3 min | +6 min |