Os 5354 5354 Slatiňany – Pardubice hl. n.

View line Os 5354

Slatiňany 10:39 → Pardubice hl. n. 11:05 Daily 0 h 26 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 10:39 from Slatiňany · Mon 9 Nov

Next departure 10:39 today · Slatiňany
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
90%
47/52 runs under 3 min
RT coverage: 52 full · 0 partial · 34 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
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 +9 min · last fix heading to — +8 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 15 Sept Max en route +4 min · last fix heading to — +4 min
  • Fri 2 Oct Max en route +3 min · last fix heading to — +3 min
  • Fri 18 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 29% · 15
  • On time 62% · 32
  • 3–10 min 10% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 83% T n=6
  • 100% W n=7
  • 100% T n=7
  • 63% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 52 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
10:39on time on time
10:43 / 10:44≈ on time ≈ on time
10:46≈ on time ≈ +1 min
10:48 / 10:49≈ on time ≈ +1 min
10:52≈ on time ≈ +1 min
10:55≈ 1 min early ≈ +1 min
10:59 / 11:02≈ 1 min early ≈ +1 min
11:051 min early +2 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. 11:04No data—
Sat 7 NovPardubice hl. n. 11:04No data—
Fri 6 NovPardubice centrum 11:09No data—
Thu 5 NovPardubice centrum 11:09No data—
Wed 4 NovPardubice centrum 11:09No data—
Tue 3 NovPardubice centrum 11:09No data—
Mon 2 NovPardubice centrum 11:09No data—
Sun 1 NovPardubice hl. n. 11:06No data—
Sat 31 OctPardubice hl. n. 11:06No data—
Fri 30 OctPardubice centrum 11:10No data—
Thu 29 OctPardubice centrum 11:10No data—
Wed 28 OctPardubice hl. n. 11:06No data—
Tue 27 OctPardubice centrum 11:10No data—
Mon 26 OctPardubice centrum 11:10No data—
Sun 25 OctPardubice hl. n. 11:06No data—
Sat 24 OctPardubice hl. n. 11:06No data—
Fri 23 OctPardubice centrum 11:10No data—
Thu 22 OctPardubice centrum 11:10No data—
Wed 21 OctPardubice centrum 11:10No data—
Tue 20 OctPardubice centrum 11:10No data—
Mon 19 OctPardubice centrum 11:10No data—
Sun 18 OctPardubice hl. n. 11:06No data—
Sat 17 OctPardubice hl. n. 11:06No data—
Fri 16 OctPardubice centrum 11:10No data—
Thu 15 OctPardubice centrum 11:10No data—
Wed 14 OctPardubice centrum 11:10No data—
Tue 13 OctPardubice centrum 11:10No data—
Mon 12 OctPardubice centrum 11:10No data—
Sun 11 OctPardubice hl. n. 11:06No data—
Sat 10 OctPardubice hl. n. 11:06No data—