EC 358 358 Praha-Vysočany → Furth im Wald
Alerts for train 358
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line EC 358.
EC 358 Praha-Vysočany–Furth im Wald: final delay under 3 min on 4 of its 42 runs with data in the last 90 days (10%). Median final delay: +7 min. TrainsRadar data as of 22 Nov 2026, 00:21 (GMT+1).
An alert on this phone or computer when the 358 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November No data
Next service: today 09:21 from Praha-Vysočany · Sun 22 Nov
Last 30 days
Arrival delay at Furth im Wald, 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 19 Sept Max en route +50 min · last fix heading to — +48 min
- Thu 3 Sept Max en route +28 min · last fix heading to — +27 min
- Wed 23 Sept Max en route +23 min · last fix heading to — +21 min
- Sun 30 Aug Max en route +20 min · last fix heading to — +20 min
- Thu 24 Sept Max en route +14 min · last fix heading to — +13 min
Distribution · 90 days
42 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 10% · 4
- 3–10 min 64% · 27
- 10–30 min 24% · 10
- 30+ min 2% · 1
On-time by weekday
- 0% M n=6
- 17% T n=6
- 17% W n=6
- 17% T n=6
- 0% F n=6
- 0% S n=6
- 17% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (53 stops).
Last 90 days, 43 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 |
|---|---|---|---|
| 09:21 | on time | +3 min | |
| 09:28 / 09:35 | ≈ on time | ≈ +3 min | |
| 09:39 | ≈ +1 min | ≈ +4 min | |
| 09:42 | ≈ +1 min | ≈ +4 min | |
| 09:46 | ≈ +1 min | ≈ +4 min | |
| 09:50 | ≈ +2 min | ≈ +5 min | |
| 09:52 | ≈ +2 min | ≈ +5 min | |
| 09:56 | ≈ +2 min | ≈ +5 min | |
| 09:58 | ≈ +2 min | ≈ +5 min | |
| 10:00 | ≈ +2 min | ≈ +5 min | |
| 10:01 | ≈ +2 min | ≈ +5 min | |
| 10:05 | ≈ +2 min | ≈ +5 min | |
| 10:08 | ≈ +2 min | ≈ +5 min | |
| 10:11 | ≈ +3 min | ≈ +5 min | |
| 10:14 | ≈ +3 min | ≈ +6 min | |
| 10:18 | ≈ +3 min | ≈ +6 min | |
| 10:23 | ≈ +3 min | ≈ +6 min | |
| 10:25 | ≈ +3 min | ≈ +6 min | |
| 10:27 | ≈ +3 min | ≈ +7 min | |
| 10:29 | ≈ +3 min | ≈ +7 min | |
| 10:32 | ≈ +4 min | ≈ +7 min | |
| 10:34 | ≈ +4 min | ≈ +7 min | |
| 10:36 | ≈ +4 min | ≈ +7 min | |
| 10:40 | ≈ +4 min | ≈ +7 min | |
| 10:41 | ≈ +4 min | ≈ +7 min | |
| 10:42 | ≈ +4 min | ≈ +7 min | |
| 10:44 | ≈ +4 min | ≈ +7 min | |
| 10:46 | ≈ +4 min | ≈ +7 min | |
| 10:49 | ≈ +4 min | ≈ +7 min | |
| 10:51 | ≈ +4 min | ≈ +7 min | |
| 10:52 | ≈ +4 min | ≈ +7 min | |
| 10:56 | ≈ +4 min | ≈ +8 min | |
| 10:58 / 11:10 | ≈ +4 min | ≈ +8 min | |
| 11:12 | ≈ +4 min | ≈ +8 min | |
| 11:13 | ≈ +5 min | ≈ +8 min | |
| 11:16 | ≈ +5 min | ≈ +8 min | |
| 11:18 | ≈ +5 min | ≈ +8 min | |
| 11:21 | ≈ +5 min | ≈ +9 min | |
| 11:24 | ≈ +5 min | ≈ +9 min | |
| 11:26 | ≈ +5 min | ≈ +9 min | |
| 11:30 | ≈ +5 min | ≈ +9 min | |
| 11:32 | ≈ +5 min | ≈ +9 min | |
| 11:37 / 11:38 | ≈ +5 min | ≈ +10 min | |
| 11:40 | ≈ +5 min | ≈ +10 min | |
| 11:43 | ≈ +5 min | ≈ +10 min | |
| 11:46 | ≈ +5 min | ≈ +10 min | |
| 11:48 | ≈ +5 min | ≈ +10 min | |
| 11:52 | ≈ +5 min | ≈ +11 min | |
| 11:58 / 12:01 | ≈ +6 min | ≈ +11 min | |
| 12:02 | ≈ +6 min | ≈ +11 min | |
| 12:08 | ≈ +6 min | ≈ +12 min | |
| 12:10 | ≈ +6 min | ≈ +12 min | |
| 12:20 | +6 min | +13 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 21 Nov | Furth im Wald 12:19 | No data | — |
| Fri 20 Nov | Furth im Wald 12:19 | No data | — |
| Thu 19 Nov | Furth im Wald 12:19 | No data | — |
| Wed 18 Nov | Furth im Wald 12:19 | No data | — |
| Tue 17 Nov | Furth im Wald 12:19 | No data | — |
| Mon 16 Nov | Furth im Wald 12:19 | No data | — |
| Sun 15 Nov | Furth im Wald 12:20 | No data | — |
| Sat 14 Nov | Furth im Wald 12:19 | No data | — |
| Fri 13 Nov | Furth im Wald 12:19 | No data | — |
| Thu 12 Nov | Furth im Wald 12:19 | No data | — |
| Wed 11 Nov | Furth im Wald 12:19 | No data | — |
| Tue 10 Nov | Furth im Wald 12:19 | No data | — |
| Mon 9 Nov | Furth im Wald 12:19 | No data | — |
| Sun 8 Nov | Furth im Wald 12:19 | No data | — |
| Sat 7 Nov | Furth im Wald 12:19 | No data | — |
| Fri 6 Nov | Furth im Wald 12:19 | No data | — |
| Thu 5 Nov | Furth im Wald 12:19 | No data | — |
| Wed 4 Nov | Furth im Wald 12:19 | No data | — |
| Tue 3 Nov | Furth im Wald 12:19 | No data | — |
| Mon 2 Nov | Furth im Wald 12:19 | No data | — |
| Sun 1 Nov | Furth im Wald 12:21 | No data | — |
| Sat 31 Oct | Furth im Wald 12:21 | No data | — |
| Fri 30 Oct | Furth im Wald 12:21 | No data | — |
| Thu 29 Oct | Furth im Wald 12:21 | No data | — |
| Wed 28 Oct | Furth im Wald 12:21 | No data | — |
| Tue 27 Oct | Furth im Wald 12:21 | No data | — |
| Mon 26 Oct | Furth im Wald 12:21 | No data | — |
| Sun 25 Oct | Furth im Wald 12:21 | No data | — |
| Sat 24 Oct | Furth im Wald 12:21 | No data | — |
| Fri 23 Oct | Furth im Wald 12:21 | No data | — |