Os 5341 5341 Pardubice hl. n. → Chrudim

View line Os 5341

Pardubice hl. n. 17:23 → Chrudim 17:44 Daily 0 h 21 min · 7 stops České dráhy, a.s.

Os 5341 Pardubice hl. n.–Chrudim: final delay under 3 min on 16 of its 41 runs with data in the last 90 days (39%). Median final delay: +4 min. TrainsRadar data as of 22 Nov 2026, 13:37 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November No data

Next service: today 17:23 from Pardubice hl. n. · Sun 22 Nov

Next departure 17:23 today · Pardubice hl. n.
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
39%
16/41 runs under 3 min
RT coverage: 41 full · 0 partial · 48 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+14min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Chrudim, in minutes. One bar per run.

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

Worst days

  • Fri 18 Sept Max en route +25 min · last fix heading to — +25 min
  • Fri 11 Sept Max en route +24 min · last fix heading to — +24 min
  • Thu 10 Sept Max en route +17 min · last fix heading to — +17 min
  • Fri 4 Sept Max en route +14 min · last fix heading to — +14 min
  • Wed 26 Aug Max en route +15 min · last fix heading to — +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 39% · 16
  • 3–10 min 46% · 19
  • 10–30 min 15% · 6
  • 30+ min 0% · 0

On-time by weekday

  • 20% M n=5
  • 17% T n=6
  • 17% W n=6
  • 33% T n=6
  • 0% F n=6
  • 100% S n=6
  • 83% S n=6

Stops and timetable

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

Last 90 days, 41 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 10
17:23on time +2 min
17:26 / 17:29≈ +1 min ≈ +3 min
17:31≈ +2 min ≈ +5 min
17:34≈ +2 min ≈ +7 min
17:38≈ +3 min ≈ +10 min
17:41≈ +3 min ≈ +12 min
17:44+4 min +14 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
Sat 21 NovChrudim 17:44No data—
Fri 20 NovSkuteč 18:19No data—
Thu 19 NovSkuteč 18:19No data—
Wed 18 NovSkuteč 18:19No data—
Tue 17 NovChrudim 17:44No data—
Mon 16 NovSkuteč 18:19No data—
Sun 15 NovChrudim 17:44No data—
Sat 14 NovChrudim 17:44No data—
Fri 13 NovSkuteč 18:19No data—
Thu 12 NovSkuteč 18:19No data—
Wed 11 NovSkuteč 18:19No data—
Tue 10 NovSkuteč 18:19No data—
Mon 9 NovSkuteč 18:19No data—
Sun 8 NovChrudim 17:44No data—
Sat 7 NovChrudim 17:44No data—
Fri 6 NovSkuteč 18:19No data—
Thu 5 NovSkuteč 18:19No data—
Wed 4 NovSkuteč 18:19No data—
Tue 3 NovSkuteč 18:19No data—
Mon 2 NovSkuteč 18:19No data—
Sun 1 NovChrudim 17:45No data—
Sat 31 OctChrudim 17:45No data—
Fri 30 OctSkuteč 18:21No data—
Thu 29 OctSkuteč 18:21No data—
Wed 28 OctChrudim 17:45No data—
Tue 27 OctSkuteč 18:22No data—
Mon 26 OctSkuteč 18:21No data—
Sun 25 OctChrudim 17:45No data—
Sat 24 OctChrudim 17:45No data—
Fri 23 OctSkuteč 18:22No data—