Os 20987 20987 Bad Brambach – Cheb
Alerts for train 20987
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 20987.
✓ Today’s run finished
Today, last fix heading to Cheb at 17:54 No data
- Bad Brambach17:25
- Plesná17:29
- Vojtanov17:36
- Žírovice-Seníky17:41
- Františkovy Lázně17:46
- Františkovy Lázně-Aquaforum17:49
- Cheb17:55
Next service: tomorrow 17:25 from Bad Brambach · Mon 9 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
- Thu 13 Aug Max en route +15 min · last fix heading to — +15 min
- Wed 12 Aug Max en route +16 min · last fix heading to — +14 min
- Sat 29 Aug Max en route +12 min · last fix heading to — +12 min
- Tue 18 Aug Max en route +10 min · last fix heading to — +10 min
- Sun 6 Sept Max en route +9 min · last fix heading to — +9 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 18% · 10
- 3–10 min 75% · 41
- 10–30 min 7% · 4
- 30+ min 0% · 0
On-time by weekday
- 14% M n=7
- 13% T n=8
- 38% W n=8
- 13% T n=8
- 0% F n=8
- 25% S n=8
- 25% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 55 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 |
|---|---|---|---|
| 17:25 | on time | +6 min | |
| 17:29 | ≈ +1 min | ≈ +7 min | |
| 17:36 / 17:37 | ≈ +2 min | ≈ +6 min | |
| 17:41 | ≈ +2 min | ≈ +7 min | |
| 17:46 / 17:48 | ≈ +3 min | ≈ +7 min | |
| 17:49 | ≈ +3 min | ≈ +8 min | |
| 17:55 | +4 min | +9 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 |
|---|---|---|---|
| Sun 8 Nov | Cheb 17:54 | No data | — |
| Sat 7 Nov | Cheb 17:54 | No data | — |
| Fri 6 Nov | Cheb 17:54 | No data | — |
| Thu 5 Nov | Cheb 17:54 | No data | — |
| Wed 4 Nov | Cheb 17:54 | No data | — |
| Tue 3 Nov | Cheb 17:54 | No data | — |
| Mon 2 Nov | Cheb 17:54 | No data | — |
| Sun 1 Nov | Cheb 17:56 | No data | — |
| Sat 31 Oct | Cheb 17:56 | No data | — |
| Fri 30 Oct | Cheb 17:56 | No data | — |
| Thu 29 Oct | Cheb 17:56 | No data | — |
| Wed 28 Oct | Cheb 17:56 | No data | — |
| Tue 27 Oct | Cheb 17:57 | No data | — |
| Mon 26 Oct | Cheb 17:56 | No data | — |
| Sun 25 Oct | Cheb 17:56 | No data | — |
| Sat 24 Oct | Cheb 17:57 | No data | — |
| Fri 23 Oct | Cheb 17:57 | No data | — |
| Thu 22 Oct | Cheb 17:56 | No data | — |
| Wed 21 Oct | Cheb 17:56 | No data | — |
| Tue 20 Oct | Cheb 17:57 | No data | — |
| Mon 19 Oct | Cheb 17:56 | No data | — |
| Sun 18 Oct | Cheb 17:56 | No data | — |
| Sat 17 Oct | Cheb 17:56 | No data | — |
| Fri 16 Oct | Cheb 17:56 | No data | — |
| Thu 15 Oct | Cheb 17:56 | No data | — |
| Wed 14 Oct | Cheb 17:56 | No data | — |
| Tue 13 Oct | Cheb 17:56 | No data | — |
| Mon 12 Oct | Cheb 17:57 | No data | — |
| Sun 11 Oct | Cheb 17:56 | No data | — |
| Sat 10 Oct | Cheb 17:56 | No data | — |