LAN 832
View line LAN
Alerts for train 832
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line LAN.
The mini-map returns when the train runs
On-time · 30 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 6 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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
- Tue 13 Oct Max en route +20 min · last fix heading to septa-rail:90720 +19 min
- Wed 14 Oct Max en route +9 min · last fix heading to septa-rail:1 +5 min
- Fri 23 Oct Max en route +8 min · last fix heading to septa-rail:90417 +4 min
- Wed 7 Oct Max en route +26 min · last fix heading to septa-rail:90815 +4 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 78% · 14
- 3–10 min 17% · 3
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 67% T n=3
- 33% W n=3
- 100% T n=3
- 67% F n=3
- 100% S n=2
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 24 Oct | septa-rail:90531 01:32 | +1 min | +6 min |
| Fri 23 Oct | septa-rail:90417 22:04 | +4 min | +8 min |
| Thu 22 Oct | septa-rail:90007 22:19 | 0 min | +20 min |
| Wed 21 Oct | septa-rail:90406 13:57 | +1 min | +5 min |
| Tue 20 Oct | septa-rail:90327 18:52 | 0 min | +3 min |
| Mon 19 Oct | septa-rail:90327 18:56 | 0 min | +13 min |
| Sun 18 Oct | septa-rail:1 00:24 | +1 min | +24 min |
| Sat 17 Oct | septa-rail:1 21:55 | 0 min | +4 min |
| Fri 16 Oct | septa-rail:90327 10:41 | +1 min | +7 min |
| Thu 15 Oct | septa-rail:90007 00:22 | 0 min | +5 min |
| Wed 14 Oct | septa-rail:1 08:41 | +5 min | +9 min |
| Tue 13 Oct | septa-rail:90720 15:33 | +19 min | +20 min |
| Mon 12 Oct | septa-rail:90531 17:25 | 0 min | +7 min |
| Fri 9 Oct | septa-rail:1 09:33 | 0 min | +7 min |
| Thu 8 Oct | septa-rail:90007 23:54 | 0 min | +4 min |
| Wed 7 Oct | septa-rail:90815 23:09 | +4 min | +26 min |
| Tue 6 Oct | septa-rail:90411 00:02 | 0 min | +10 min |
| Mon 5 Oct | septa-rail:1 23:33 | 0 min | +5 min |
| Sun 4 Oct | 1 23:03 | No data | — |
| Sat 3 Oct | 1 21:07 | No data | — |
| Fri 2 Oct | 1 16:04 | No data | — |
| Thu 1 Oct | 1 16:43 | No data | — |
| Wed 30 Sept | 1 18:33 | No data | — |
| Tue 29 Sept | 1 17:53 | No data | — |
| Fri 25 Sept | 90006 12:43 | No data | — |
| Wed 23 Sept | 90327 16:35 | No data | — |
| Tue 22 Sept | 90720 19:20 | No data | — |
| Mon 21 Sept | 90007 08:16 | No data | — |
| Sun 20 Sept | 90522 07:15 | No data | — |
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.