PAO 356
View line PAO
Alerts for train 356
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line PAO.
The mini-map returns when the train runs
On-time · 30 days
64%
16/25 runs under 3 min
RT coverage: 25 full · 0 partial · 2 no data
On-time · 90 days
49%
32/65 runs under 3 min
RT coverage: 65 full · 0 partial · 2 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +2 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +9 min
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
- Fri 24 Jul Max en route +23 min · last fix heading to 171 +23 min
- Tue 13 Oct Max en route +40 min · last fix heading to septa-rail:90326 +22 min
- Sun 18 Oct Max en route +13 min · last fix heading to septa-rail:90005 +11 min
- Sun 11 Oct Max en route +15 min · last fix heading to septa-rail:1 +11 min
- Tue 1 Sept Max en route +10 min · last fix heading to 171 +10 min
Distribution · 90 days
65 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 49% · 32
- 3–10 min 43% · 28
- 10–30 min 8% · 5
- 30+ min 0% · 0
On-time by weekday
- 64% M n=11
- 46% T n=13
- 33% W n=12
- 75% T n=12
- 38% F n=13
- 50% S n=2
- 0% S n=2
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 20 Oct | septa-rail:90007 05:52 | 0 min | +7 min |
| Mon 19 Oct | septa-rail:1 21:29 | +1 min | +13 min |
| Sun 18 Oct | septa-rail:90005 23:06 | +11 min | +13 min |
| Sat 17 Oct | septa-rail:1 14:50 | +7 min | +11 min |
| Fri 16 Oct | septa-rail:90720 23:17 | +3 min | +10 min |
| Thu 15 Oct | septa-rail:90302 21:00 | 0 min | +11 min |
| Wed 14 Oct | septa-rail:90007 21:20 | 0 min | +13 min |
| Tue 13 Oct | septa-rail:90326 10:57 | +22 min | +40 min |
| Mon 12 Oct | septa-rail:90007 21:20 | 0 min | +25 min |
| Sun 11 Oct | septa-rail:1 22:08 | +11 min | +15 min |
| Sat 10 Oct | septa-rail:90007 00:06 | +1 min | +47 min |
| Fri 9 Oct | septa-rail:1 22:45 | 0 min | +18 min |
| Thu 8 Oct | septa-rail:1 00:36 | 0 min | +21 min |
| Wed 7 Oct | septa-rail:90406 23:49 | +1 min | +5 min |
| Tue 6 Oct | septa-rail:90719 23:13 | 0 min | +33 min |
| Mon 5 Oct | septa-rail:1 22:51 | +4 min | +6 min |
| Sun 4 Oct | 90006 23:27 | No data | — |
| Sat 3 Oct | 90007 19:40 | No data | — |
| Fri 2 Oct | 90007 18:34 | +2 min | +2 min |
| Thu 1 Oct | 90007 19:48 | +3 min | +3 min |
| Wed 30 Sept | 171 16:34 | +4 min | +4 min |
| Tue 29 Sept | 171 16:34 | +2 min | +3 min |
| Mon 28 Sept | 171 16:32 | +2 min | +2 min |
| Fri 25 Sept | 171 16:35 | +4 min | +4 min |
| Thu 24 Sept | 171 16:34 | +3 min | +3 min |
| Wed 23 Sept | 171 16:33 | +3 min | +4 min |
| Tue 22 Sept | 171 16:33 | +3 min | +3 min |
| Mon 21 Sept | 171 16:33 | +3 min | +3 min |
| Fri 18 Sept | 171 16:35 | +5 min | +5 min |
| Thu 17 Sept | 171 16:35 | +4 min | +4 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.