RE 50242
View line RE
Alerts for train 50242
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RE.
It does not run today
Last recorded run: Thursday 8 October No data
The mini-map returns when the train runs
On-time ยท 30 days
โ
Too little data (0/8 runs with data)
RT coverage: 0 full ยท 0 partial ยท 8 no data
On-time ยท 90 days
โ
Too little data (0/8 runs with data)
RT coverage: 0 full ยท 0 partial ยท 8 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 |
|---|---|---|---|
| Thu 8 Oct | CPH Lufthavn 16:53 | No data | โ |
| Wed 7 Oct | CPH Lufthavn 16:53 | No data | โ |
| Tue 6 Oct | CPH Lufthavn 16:53 | No data | โ |
| Mon 5 Oct | CPH Lufthavn 16:53 | No data | โ |
| Thu 1 Oct | CPH Lufthavn 17:01 | No data | โ |
| Wed 30 Sept | CPH Lufthavn 17:01 | No data | โ |
| Tue 29 Sept | CPH Lufthavn 17:01 | No data | โ |
| Mon 28 Sept | CPH Lufthavn 17:01 | 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 14 September 2026.