Os 5360 5360 Chrudim – Pardubice centrum

View line Os 5360

Chrudim 19:11 → Pardubice centrum 19:37 Daily 0 h 26 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 19:11 from Chrudim · Tue 10 Nov

Next departure 19:11 today · Chrudim
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
57%
30/53 runs under 3 min
RT coverage: 53 full · 0 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
P90
+6min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Pardubice centrum, 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 6 Sept Max en route +12 min · last fix heading to — +12 min
  • Mon 28 Sept Max en route +9 min · last fix heading to — +9 min
  • Mon 17 Aug Max en route +11 min · last fix heading to — +8 min
  • Fri 4 Sept Max en route +9 min · last fix heading to — +7 min
  • Tue 8 Sept Max en route +8 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 21% · 11
  • On time 36% · 19
  • 3–10 min 42% · 22
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 43% M n=7
  • 43% T n=7
  • 57% W n=7
  • 88% T n=8
  • 50% F n=8
  • 50% S n=8
  • 63% S n=8

Stops and timetable

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

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