Os 20822 20822 Sokolov – Klingenthal
Alerts for train 20822
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 20822.
It has not run yet today
Last recorded run: Friday 6 November No data
Next service: today 14:32 from Sokolov · Sat 7 Nov
Last 30 days
Arrival delay at Klingenthal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 3 Oct Max en route +31 min · last fix heading to — +29 min
- Wed 26 Aug Max en route +17 min · last fix heading to — +17 min
- Sat 19 Sept Max en route +8 min · last fix heading to — +8 min
- Fri 21 Aug Max en route +9 min · last fix heading to — +8 min
- Thu 27 Aug Max en route +9 min · last fix heading to — +6 min
Distribution · 90 days
57 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 84% · 48
- 3–10 min 12% · 7
- 10–30 min 4% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=9
- 100% T n=8
- 88% W n=8
- 75% T n=8
- 75% F n=8
- 63% S n=8
- 88% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 57 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 |
|---|---|---|---|
| 14:32 | on time | +6 min | |
| 14:34 / 14:35 | ≈ on time | ≈ +6 min | |
| 14:37 | ≈ on time | ≈ +5 min | |
| 14:41 | ≈ +1 min | ≈ +5 min | |
| 14:43 / 14:44 | ≈ +1 min | ≈ +5 min | |
| 14:51 / 14:52 | ≈ +1 min | ≈ +4 min | |
| 14:58 / 14:59 | ≈ +1 min | ≈ +4 min | |
| 15:04 | ≈ on time | ≈ +3 min | |
| 15:08 / 15:09 | ≈ on time | ≈ +3 min | |
| 15:10 | ≈ on time | ≈ +3 min | |
| 15:14 | on time | +3 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 |
|---|---|---|---|
| Fri 6 Nov | Klingenthal 15:14 | No data | — |
| Thu 5 Nov | Klingenthal 15:14 | No data | — |
| Wed 4 Nov | Klingenthal 15:15 | No data | — |
| Tue 3 Nov | Klingenthal 15:14 | No data | — |
| Mon 2 Nov | Klingenthal 15:14 | No data | — |
| Sun 1 Nov | Klingenthal 15:15 | No data | — |
| Sat 31 Oct | Klingenthal 15:15 | No data | — |
| Fri 30 Oct | Klingenthal 15:15 | No data | — |
| Thu 29 Oct | Klingenthal 15:15 | No data | — |
| Wed 28 Oct | Klingenthal 15:15 | No data | — |
| Tue 27 Oct | Klingenthal 15:15 | No data | — |
| Mon 26 Oct | Klingenthal 15:15 | No data | — |
| Sun 25 Oct | Klingenthal 15:15 | No data | — |
| Sat 24 Oct | Klingenthal 15:15 | No data | — |
| Fri 23 Oct | Klingenthal 15:15 | No data | — |
| Thu 22 Oct | Klingenthal 15:15 | No data | — |
| Wed 21 Oct | Klingenthal 15:15 | No data | — |
| Tue 20 Oct | Klingenthal 15:15 | No data | — |
| Mon 19 Oct | Klingenthal 15:15 | No data | — |
| Sun 18 Oct | Klingenthal 15:15 | No data | — |
| Sat 17 Oct | Klingenthal 15:15 | No data | — |
| Fri 16 Oct | Klingenthal 15:15 | No data | — |
| Thu 15 Oct | Klingenthal 15:15 | No data | — |
| Wed 14 Oct | Klingenthal 15:15 | No data | — |
| Tue 13 Oct | Klingenthal 15:15 | No data | — |
| Mon 12 Oct | Klingenthal 15:15 | No data | — |
| Sun 11 Oct | Klingenthal 15:15 | No data | — |
| Sat 10 Oct | Klingenthal 15:15 | No data | — |
| Fri 9 Oct | Klingenthal 15:15 | No data | — |
| Thu 8 Oct | Klingenthal 15:15 | No data | — |