Os 27219 27219 Luby u Chebu – Cheb
Alerts for train 27219
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 27219.
It has not run yet today
Last recorded run: Monday 9 November No data
Next service: today 20:42 from Luby u Chebu · Tue 10 Nov
Last 30 days
Arrival delay at Cheb, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 6 Sept Max en route +23 min · last fix heading to — +22 min
- Tue 22 Sept Max en route +10 min · last fix heading to — +10 min
- Mon 14 Sept Max en route +9 min · last fix heading to — +9 min
- Fri 2 Oct Max en route +8 min · last fix heading to — +8 min
- Mon 21 Sept Max en route +8 min · last fix heading to — +8 min
Distribution · 90 days
53 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 4% · 2
- On time 49% · 26
- 3–10 min 43% · 23
- 10–30 min 4% · 2
- 30+ min 0% · 0
On-time by weekday
- 43% M n=7
- 57% T n=7
- 57% W n=7
- 75% T n=8
- 25% F n=8
- 50% S n=8
- 63% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 53 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 20:42 | on time | +2 min | |
| 20:45 | ≈ on time | ≈ +2 min | |
| 20:48 | ≈ on time | ≈ +2 min | |
| 20:54 | ≈ +1 min | ≈ +3 min | |
| 20:59 / 21:00 | ≈ +1 min | ≈ +4 min | |
| 21:02 | ≈ +1 min | ≈ +4 min | |
| 21:05 | ≈ +1 min | ≈ +5 min | |
| 21:07 | ≈ +1 min | ≈ +5 min | |
| 21:10 / 21:11 | ≈ +2 min | ≈ +6 min | |
| 21:18 | +2 min | +7 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 11 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Cheb 21:19 | No data | — |
| Sun 8 Nov | Cheb 21:19 | No data | — |
| Sat 7 Nov | Cheb 21:19 | No data | — |
| Fri 6 Nov | Cheb 21:19 | No data | — |
| Thu 5 Nov | Cheb 21:19 | No data | — |
| Wed 4 Nov | Cheb 21:19 | No data | — |
| Tue 3 Nov | Cheb 21:19 | No data | — |
| Mon 2 Nov | Cheb 21:19 | No data | — |
| Sun 1 Nov | Cheb 21:19 | No data | — |
| Sat 31 Oct | Cheb 21:19 | No data | — |
| Fri 30 Oct | Cheb 21:19 | No data | — |
| Thu 29 Oct | Cheb 21:19 | No data | — |
| Wed 28 Oct | Cheb 21:19 | No data | — |
| Tue 27 Oct | Cheb 21:20 | No data | — |
| Mon 26 Oct | Cheb 21:19 | No data | — |
| Sun 25 Oct | Cheb 21:20 | No data | — |
| Sat 24 Oct | Cheb 21:19 | No data | — |
| Fri 23 Oct | Cheb 21:19 | No data | — |
| Thu 22 Oct | Cheb 21:19 | No data | — |
| Wed 21 Oct | Cheb 21:19 | No data | — |
| Tue 20 Oct | Cheb 21:19 | No data | — |
| Mon 19 Oct | Cheb 21:20 | No data | — |
| Sun 18 Oct | Cheb 21:19 | No data | — |
| Sat 17 Oct | Cheb 21:19 | No data | — |
| Fri 16 Oct | Cheb 21:19 | No data | — |
| Thu 15 Oct | Cheb 21:19 | No data | — |
| Wed 14 Oct | Cheb 21:19 | No data | — |
| Tue 13 Oct | Cheb 21:19 | No data | — |
| Mon 12 Oct | Cheb 21:20 | No data | — |
| Sun 11 Oct | Cheb 21:19 | No data | — |