WAR 277
Alerts for train 277
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line WAR.
431,432,277: final delay under 3 min on 3 of its 6 runs with data in the last 30 days (50%). Median final delay: +3 min. Running now, 2 min late. TrainsRadar data as of 21 Nov 2026, 06:24 (GMT-5).
An alert on this phone or computer when the 277 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 06:23
Running now +2 min
Today it is running no worse than usual: typical arrival delay is +3 min; 50% of the last 6 runs arrived on time.
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
- Thu 29 Oct Max en route +22 min · last fix heading to septa-rail:1 +16 min
- Wed 21 Oct Max en route +9 min · last fix heading to septa-rail:90203 +9 min
- Wed 28 Oct Max en route +12 min · last fix heading to septa-rail:90505 +5 min
- Sat 21 Nov Max en route +8 min · last fix heading to septa-rail:90413 +4 min
- Thu 22 Oct Max en route +14 min · last fix heading to septa-rail:90801 +3 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 24
- 3–10 min 14% · 4
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=6
- 67% W n=6
- 75% T n=8
- 100% F n=2
- 0% S n=1
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | septa-rail:90413 06:19 | +4 min | +8 min |
| Thu 29 Oct | septa-rail:1 07:56 | +16 min | +22 min |
| Wed 28 Oct | septa-rail:90505 20:14 | +5 min | +12 min |
| Tue 27 Oct | septa-rail:1 22:49 | 0 min | +32 min |
| Mon 26 Oct | septa-rail:1 21:30 | +2 min | +19 min |
| Fri 23 Oct | septa-rail:1 23:35 | +1 min | +7 min |
| Thu 22 Oct | septa-rail:90801 18:04 | +3 min | +14 min |
| Wed 21 Oct | septa-rail:90203 09:40 | +9 min | +9 min |
| Tue 20 Oct | septa-rail:1 23:39 | 0 min | +20 min |
| Thu 1 Oct | WR-0099-01 19:58 | 0 min | — |
| Wed 30 Sept | WR-0085-01 19:59 | 0 min | — |
| Tue 29 Sept | WR-0099-01 19:59 | 0 min | — |
| Sun 27 Sept | WR-0099-01 19:59 | 0 min | — |
| Fri 25 Sept | WR-0085-01 19:59 | 0 min | — |
| Thu 24 Sept | WR-0099-01 19:59 | 0 min | — |
| Tue 22 Sept | WR-0099-01 19:59 | 0 min | — |
| Mon 21 Sept | WR-0099-01 19:58 | 0 min | — |
| Thu 17 Sept | WR-0099-01 19:59 | 0 min | — |
| Tue 15 Sept | WR-0099-01 19:59 | 0 min | — |
| Mon 14 Sept | WR-0120-S 19:59 | 0 min | — |
| Thu 10 Sept | WR-0099-01 19:58 | 0 min | — |
| Wed 9 Sept | WR-0099-01 19:58 | 0 min | — |
| Tue 8 Sept | WR-0099-01 19:59 | 0 min | — |
| Thu 3 Sept | WR-0099-01 19:59 | 0 min | — |
| Wed 2 Sept | WR-0099-01 19:59 | 0 min | — |
| Mon 31 Aug | WR-0099-01 19:59 | 0 min | — |
| Thu 27 Aug | WR-0099-01 19:59 | 0 min | — |
| Wed 26 Aug | WR-0099-01 19:59 | 0 min | — |
| Mon 24 Aug | WR-0099-01 19:59 | 0 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.