EC 353 353 Furth im Wald → Praha-Vysočany

View line EC 353

Furth im Wald 09:40 → Praha-Vysočany 12:34 Daily 2 h 54 min · 53 stops Die Länderbahn GmbH DLB

EC 353 Furth im Wald–Praha-Vysočany: final delay under 3 min on 22 of its 42 runs with data in the last 90 days (52%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 12:05 (GMT+1).

Running now · updated 12:05

Position estimated from the timetable

Between Praha-Radotín and Praha-Velká Chuchle No data

Estimated arrival at Praha-Vysočany 12:34 · 65 km/h

  1. Furth im Wald09:40
  2. Dolní Kamenice10:19
  3. Vejprnice10:41
  4. Holoubkov11:15
  5. Praha-Radotín12:03
  6. Praha-Velká Chuchle12:06
  7. Praha-Vysočany12:34
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
52%
22/42 runs under 3 min
RT coverage: 42 full · 0 partial · 48 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+23min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Praha-Vysočany, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 26 Aug Max en route +54 min · last fix heading to — +53 min
  • Fri 28 Aug Max en route +38 min · last fix heading to — +31 min
  • Wed 30 Sept Max en route +26 min · last fix heading to — +25 min
  • Fri 18 Sept Max en route +29 min · last fix heading to — +24 min
  • Tue 29 Sept Max en route +33 min · last fix heading to — +23 min

Distribution · 90 days

42 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 26% · 11
  • On time 26% · 11
  • 3–10 min 17% · 7
  • 10–30 min 26% · 11
  • 30+ min 5% · 2

On-time by weekday

  • 33% M n=6
  • 67% T n=6
  • 17% W n=6
  • 83% T n=6
  • 33% F n=6
  • 67% S n=6
  • 67% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (53 stops).

Last 90 days, 42 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.

StopSched.Usually 9 days in 10Today
09:40+8 min +19 minPassed
09:50≈ +7 min ≈ +18 minPassed
09:52≈ +7 min ≈ +18 minPassed
09:57≈ +7 min ≈ +18 minPassed
09:59 / 10:01≈ +7 min ≈ +18 minPassed
10:07≈ +7 min ≈ +19 minPassed
10:10≈ +7 min ≈ +19 minPassed
10:13≈ +7 min ≈ +19 minPassed
10:15≈ +7 min ≈ +19 minPassed
10:19≈ +7 min ≈ +20 minPassed
10:21 / 10:22≈ +7 min ≈ +20 minPassed
10:26≈ +7 min ≈ +20 minPassed
10:28≈ +7 min ≈ +20 minPassed
10:30≈ +7 min ≈ +20 minPassed
10:33≈ +7 min ≈ +20 minPassed
10:37≈ +7 min ≈ +20 minPassed
10:39≈ +6 min ≈ +20 minPassed
10:41≈ +6 min ≈ +20 minPassed
10:44≈ +6 min ≈ +20 minPassed
10:45≈ +6 min ≈ +20 minPassed
10:47 / 11:00≈ +6 min ≈ +20 minPassed
11:02≈ +6 min ≈ +20 minPassed
11:07≈ +6 min ≈ +20 minPassed
11:08≈ +6 min ≈ +20 minPassed
11:10≈ +6 min ≈ +20 minPassed
11:12≈ +6 min ≈ +20 minPassed
11:15≈ +5 min ≈ +20 minPassed
11:16≈ +5 min ≈ +20 minPassed
11:18≈ +5 min ≈ +20 minPassed
11:19≈ +5 min ≈ +20 minPassed
11:22≈ +5 min ≈ +20 minPassed
11:25≈ +5 min ≈ +20 minPassed
11:27≈ +5 min ≈ +20 minPassed
11:28≈ +5 min ≈ +20 minPassed
11:30≈ +4 min ≈ +20 minPassed
11:32≈ +4 min ≈ +20 minPassed
11:33≈ +4 min ≈ +20 minPassed
11:37≈ +4 min ≈ +20 minPassed
11:42≈ +4 min ≈ +20 minPassed
11:47≈ +3 min ≈ +20 minPassed
11:50≈ +3 min ≈ +21 minPassed
11:52≈ +3 min ≈ +21 minPassed
11:55≈ +3 min ≈ +21 minPassed
11:56≈ +3 min ≈ +21 minPassed
11:58≈ +2 min ≈ +21 minPassed
12:00≈ +2 min ≈ +21 minPassed
12:03≈ +2 min ≈ +22 minPassed
12:06≈ +2 min ≈ +22 minNext
12:13≈ +2 min ≈ +23 min
12:14≈ +1 min ≈ +23 min
12:17≈ +1 min ≈ +23 min
12:21 / 12:28≈ +1 min ≈ +23 min
12:34+1 min +23 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

DateLast stopFinalMax
Sun 22 NovPraha-Velká Chuchle 12:04Partial coverageNo data—
Sat 21 NovPraha-Vysočany 12:34No data—
Fri 20 NovPraha-Vysočany 12:34No data—
Thu 19 NovPraha-Vysočany 12:34No data—
Wed 18 NovPraha-Vysočany 12:34No data—
Tue 17 NovPraha-Vysočany 12:34No data—
Mon 16 NovPraha-Vysočany 12:34No data—
Sun 15 NovPraha-Vysočany 12:34No data—
Sat 14 NovPraha-Vysočany 12:34No data—
Fri 13 NovPraha-Vysočany 12:34No data—
Thu 12 NovPraha-Vysočany 12:34No data—
Wed 11 NovPraha-Vysočany 12:34No data—
Tue 10 NovPraha-Vysočany 12:34No data—
Mon 9 NovPraha-Vysočany 12:34No data—
Sun 8 NovPraha-Vysočany 12:34No data—
Sat 7 NovPraha-Vysočany 12:34No data—
Fri 6 NovPraha-Vysočany 12:34No data—
Thu 5 NovPraha-Vysočany 12:34No data—
Wed 4 NovPraha-Vysočany 12:34No data—
Tue 3 NovPraha-Vysočany 12:34No data—
Mon 2 NovPraha-Vysočany 12:34No data—
Sun 1 NovPraha-Vysočany 12:35No data—
Sat 31 OctPraha-Vysočany 12:35No data—
Fri 30 OctPraha-Vysočany 12:35No data—
Thu 29 OctPraha-Vysočany 12:35No data—
Wed 28 OctPraha-Vysočany 12:35No data—
Tue 27 OctPraha-Vysočany 12:35No data—
Mon 26 OctPraha-Vysočany 12:35No data—
Sun 25 OctPraha-Vysočany 12:35No data—
Sat 24 OctPraha-Vysočany 12:35No data—