IC 558 558 Praha-Vysočany – Cheb
Alerts for train 558
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line IC 558.
✓ Today’s run finished
Today, last fix heading to Cheb at 19:27 No data
- Praha-Vysočany16:23
- Dobřichovice17:01
- Praskolesy17:32
- Ejpovice17:52
- Pňovany zastávka18:19
- Planá u M.L.18:52
- Cheb19:26
Next service: tomorrow 16:23 from Praha-Vysočany · Sun 8 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 4 Oct Max en route +30 min · last fix heading to — +26 min
- Sun 6 Sept Max en route +20 min · last fix heading to — +16 min
- Wed 19 Aug Max en route +16 min · last fix heading to — +16 min
- Sat 22 Aug Max en route +12 min · last fix heading to — +12 min
- Tue 18 Aug Max en route +15 min · last fix heading to — +12 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 53% · 30
- 3–10 min 26% · 15
- 10–30 min 21% · 12
- 30+ min 0% · 0
On-time by weekday
- 67% M n=9
- 63% T n=8
- 50% W n=8
- 50% T n=8
- 38% F n=8
- 75% S n=8
- 25% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (60 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 |
|---|---|---|---|
| 16:23 | on time | +1 min | |
| 16:29 / 16:35 | ≈ on time | ≈ +1 min | |
| 16:39 | ≈ on time | ≈ +2 min | |
| 16:42 | ≈ on time | ≈ +2 min | |
| 16:46 | ≈ +1 min | ≈ +2 min | |
| 16:50 | ≈ +1 min | ≈ +2 min | |
| 16:52 | ≈ +1 min | ≈ +2 min | |
| 16:56 | ≈ +1 min | ≈ +2 min | |
| 16:58 | ≈ +1 min | ≈ +2 min | |
| 17:00 | ≈ +1 min | ≈ +2 min | |
| 17:01 | ≈ +1 min | ≈ +3 min | |
| 17:05 | ≈ +1 min | ≈ +3 min | |
| 17:08 | ≈ +1 min | ≈ +3 min | |
| 17:11 | ≈ +1 min | ≈ +3 min | |
| 17:14 | ≈ +1 min | ≈ +3 min | |
| 17:18 | ≈ +1 min | ≈ +4 min | |
| 17:23 | ≈ +1 min | ≈ +4 min | |
| 17:25 | ≈ +1 min | ≈ +4 min | |
| 17:27 | ≈ +1 min | ≈ +4 min | |
| 17:29 | ≈ +1 min | ≈ +4 min | |
| 17:32 | ≈ +1 min | ≈ +4 min | |
| 17:34 | ≈ +1 min | ≈ +5 min | |
| 17:36 | ≈ +1 min | ≈ +5 min | |
| 17:40 | ≈ +1 min | ≈ +5 min | |
| 17:41 | ≈ +1 min | ≈ +5 min | |
| 17:42 | ≈ +1 min | ≈ +5 min | |
| 17:44 | ≈ +1 min | ≈ +5 min | |
| 17:46 | ≈ +1 min | ≈ +5 min | |
| 17:49 | ≈ +1 min | ≈ +5 min | |
| 17:51 | ≈ +1 min | ≈ +6 min | |
| 17:52 | ≈ +1 min | ≈ +6 min | |
| 17:56 | ≈ +2 min | ≈ +6 min | |
| 17:58 / 18:04 | ≈ +1 min | ≈ +6 min | |
| 18:06 / 18:08 | ≈ +1 min | ≈ +6 min | |
| 18:10 | ≈ +1 min | ≈ +7 min | |
| 18:11 | ≈ +1 min | ≈ +7 min | |
| 18:12 | ≈ +1 min | ≈ +7 min | |
| 18:14 | ≈ +1 min | ≈ +7 min | |
| 18:17 | ≈ +1 min | ≈ +7 min | |
| 18:19 | ≈ +1 min | ≈ +7 min | |
| 18:21 | ≈ +1 min | ≈ +7 min | |
| 18:23 | ≈ +1 min | ≈ +7 min | |
| 18:26 | ≈ +1 min | ≈ +8 min | |
| 18:29 / 18:31 | ≈ +1 min | ≈ +8 min | |
| 18:35 | ≈ +1 min | ≈ +8 min | |
| 18:37 | ≈ +1 min | ≈ +8 min | |
| 18:41 | ≈ +2 min | ≈ +8 min | |
| 18:46 | ≈ +2 min | ≈ +9 min | |
| 18:49 | ≈ +2 min | ≈ +9 min | |
| 18:52 / 18:54 | ≈ +2 min | ≈ +9 min | |
| 18:58 / 18:59 | ≈ +2 min | ≈ +9 min | |
| 19:05 / 19:07 | ≈ +2 min | ≈ +10 min | |
| 19:09 | ≈ +2 min | ≈ +10 min | |
| 19:12 | ≈ +2 min | ≈ +10 min | |
| 19:15 | ≈ +2 min | ≈ +10 min | |
| 19:17 | ≈ +2 min | ≈ +10 min | |
| 19:19 | ≈ +2 min | ≈ +11 min | |
| 19:21 | ≈ +2 min | ≈ +11 min | |
| 19:22 | ≈ +2 min | ≈ +11 min | |
| 19:26 | +2 min | +11 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 |
|---|---|---|---|
| Sat 7 Nov | Cheb 19:27 | No data | — |
| Fri 6 Nov | Cheb 19:27 | No data | — |
| Thu 5 Nov | Cheb 19:27 | No data | — |
| Wed 4 Nov | Cheb 19:27 | No data | — |
| Tue 3 Nov | Cheb 19:27 | No data | — |
| Mon 2 Nov | Cheb 19:27 | No data | — |
| Sun 1 Nov | Cheb 19:27 | No data | — |
| Sat 31 Oct | Cheb 19:27 | No data | — |
| Fri 30 Oct | Cheb 19:27 | No data | — |
| Thu 29 Oct | Cheb 19:27 | No data | — |
| Wed 28 Oct | Cheb 19:27 | No data | — |
| Tue 27 Oct | Cheb 19:28 | No data | — |
| Mon 26 Oct | Cheb 19:27 | No data | — |
| Sun 25 Oct | Cheb 19:27 | No data | — |
| Sat 24 Oct | Cheb 19:27 | No data | — |
| Fri 23 Oct | Cheb 19:27 | No data | — |
| Thu 22 Oct | Cheb 19:27 | No data | — |
| Wed 21 Oct | Cheb 19:28 | No data | — |
| Tue 20 Oct | Cheb 19:27 | No data | — |
| Mon 19 Oct | Cheb 19:27 | No data | — |
| Sun 18 Oct | Cheb 19:27 | No data | — |
| Sat 17 Oct | Cheb 19:27 | No data | — |
| Fri 16 Oct | Cheb 19:27 | No data | — |
| Thu 15 Oct | Cheb 19:27 | No data | — |
| Wed 14 Oct | Cheb 19:27 | No data | — |
| Tue 13 Oct | Cheb 19:27 | No data | — |
| Mon 12 Oct | Cheb 19:28 | No data | — |
| Sun 11 Oct | Cheb 19:27 | No data | — |
| Sat 10 Oct | Cheb 19:27 | No data | — |
| Fri 9 Oct | Cheb 19:27 | No data | — |