S20 3070
View line S20
Alerts for train 3070
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S20.
The mini-map returns when the train runs
On-time ยท 30 days
โ
Too little data (0/7 runs with data)
RT coverage: 0 full ยท 0 partial ยท 7 no data
On-time ยท 90 days
โ
Too little data (0/7 runs with data)
RT coverage: 0 full ยท 0 partial ยท 7 no data
Typical delay
โ
Needs at least 5 runs with data (0 so far)
P90
โ
Needs at least 5 runs with data (0 so far)
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
Distribution ยท 90 days
No runs with a known final delay yet.
On-time by weekday
- โ M n=0
- โ T n=0
- โ W n=0
- โ T n=0
- โ F n=0
- โ S n=0
- โ S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 25 Oct | Louvain 21:07 | No data | โ |
| Sat 24 Oct | Louvain 21:08 | No data | โ |
| Sun 18 Oct | Louvain 21:07 | No data | โ |
| Sat 17 Oct | Louvain 21:07 | No data | โ |
| Sun 11 Oct | Louvain 21:07 | No data | โ |
| Sat 10 Oct | Louvain 21:07 | No data | โ |
| Sun 4 Oct | Louvain 21:07 | 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 3 October 2026.