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