Os 5355 5355 Pardubice hl. n. → Chrudim

View line Os 5355

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

✓ Today’s run finished

Today, last fix heading to Chrudim at 07:45 No data

  1. Pardubice hl. n.07:23
  2. Pardubice-Rosice n.L.07:26
  3. Pardubice závodiště07:31
  4. Staré Jesenčany07:34
  5. Medlešice07:38
  6. Chrudim zastávka07:41
  7. Chrudim07:44

Next service: tomorrow 07:23 from Pardubice hl. n. · Sun 22 Nov

Next departure 07:23 tomorrow · Pardubice hl. n.
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
40%
16/40 runs under 3 min
RT coverage: 40 full · 0 partial · 47 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+8min
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

  • Thu 10 Sept Max en route +17 min · last fix heading to — +17 min
  • Tue 29 Sept Max en route +12 min · last fix heading to — +12 min
  • Mon 21 Sept Max en route +10 min · last fix heading to — +9 min
  • Thu 17 Sept Max en route +10 min · last fix heading to — +9 min
  • Fri 11 Sept Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 40% · 16
  • 3–10 min 55% · 22
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 43% M n=7
  • 20% T n=5
  • 0% W n=5
  • 0% T n=5
  • 0% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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