Os 5340 5340 Chrudim – Pardubice hl. n.

View line Os 5340

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

✓ Today’s run finished

Today, last fix heading to Pardubice hl. n. at 18:34 No data

  1. Chrudim18:14
  2. Chrudim zastávka18:16
  3. Medlešice18:18
  4. Staré Jesenčany18:22
  5. Pardubice závodiště18:25
  6. Pardubice-Rosice n.L.18:29
  7. Pardubice hl. n.18:35

Next service: tomorrow 18:14 from Chrudim · Mon 9 Nov

Next departure 18:14 tomorrow · Chrudim
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
76%
42/55 runs under 3 min
RT coverage: 55 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
P90
+7min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Pardubice hl. n., 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 14 Aug Max en route +30 min · last fix heading to — +28 min
  • Mon 17 Aug Max en route +15 min · last fix heading to — +14 min
  • Fri 4 Sept Max en route +10 min · last fix heading to — +8 min
  • Fri 28 Aug Max en route +10 min · last fix heading to — +8 min
  • Fri 21 Aug Max en route +13 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 16% · 9
  • On time 60% · 33
  • 3–10 min 20% · 11
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 75% T n=8
  • 88% W n=8
  • 75% T n=8
  • 38% F n=8
  • 88% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 55 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
18:14on time +4 min
18:16≈ on time ≈ +4 min
18:18 / 18:19≈ on time ≈ +4 min
18:22≈ on time ≈ +4 min
18:25≈ on time ≈ +5 min
18:29 / 18:32≈ on time ≈ +6 min
18:35on time +7 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 8 NovPardubice hl. n. 18:34No data—
Sat 7 NovPardubice hl. n. 18:34No data—
Fri 6 NovPardubice centrum 18:39No data—
Thu 5 NovPardubice centrum 18:39No data—
Wed 4 NovPardubice centrum 18:39No data—
Tue 3 NovPardubice centrum 18:39No data—
Mon 2 NovPardubice centrum 18:39No data—
Sun 1 NovPardubice hl. n. 18:34No data—
Sat 31 OctPardubice hl. n. 18:36No data—
Fri 30 OctPardubice centrum 18:40No data—
Thu 29 OctPardubice centrum 18:40No data—
Wed 28 OctPardubice hl. n. 18:36No data—
Tue 27 OctPardubice centrum 18:41No data—
Mon 26 OctPardubice centrum 18:40No data—
Sun 25 OctPardubice hl. n. 18:36No data—
Sat 24 OctPardubice hl. n. 18:36No data—
Fri 23 OctPardubice centrum 18:41No data—
Thu 22 OctPardubice centrum 18:40No data—
Wed 21 OctPardubice centrum 18:40No data—
Tue 20 OctPardubice centrum 18:41No data—
Mon 19 OctPardubice centrum 18:40No data—
Sun 18 OctPardubice hl. n. 18:37No data—
Sat 17 OctPardubice hl. n. 18:36No data—
Fri 16 OctPardubice centrum 18:40No data—
Thu 15 OctPardubice centrum 18:40No data—
Wed 14 OctPardubice centrum 18:40No data—
Tue 13 OctPardubice centrum 18:40No data—
Mon 12 OctPardubice centrum 18:41No data—
Sun 11 OctPardubice hl. n. 18:36No data—
Sat 10 OctPardubice hl. n. 18:36No data—