Os 5337 5337 Pardubice centrum – Skuteč

View line Os 5337

Pardubice centrum 15:19 → Skuteč 16:20 Daily 1 h 01 min · 17 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Skuteč at 16:19 No data

  1. Pardubice centrum15:19
  2. Pardubice závodiště15:31
  3. Medlešice15:38
  4. Slatiňany15:49
  5. Chrast u Chrudimi15:58
  6. Vrbatův Kostelec16:07
  7. Skuteč16:20

Next service: tomorrow 15:19 from Pardubice centrum · Wed 11 Nov

Next departure 15:19 tomorrow · Pardubice centrum
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
31%
17/54 runs under 3 min
RT coverage: 54 full · 0 partial · 36 no data
Typical delay
+5min
Median at arrival, 90 days
P90
+11min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Skuteč, 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 21 Aug Max en route +21 min · last fix heading to — +21 min
  • Fri 2 Oct Max en route +17 min · last fix heading to — +16 min
  • Mon 17 Aug Max en route +15 min · last fix heading to — +15 min
  • Fri 14 Aug Max en route +14 min · last fix heading to — +14 min
  • Tue 22 Sept Max en route +12 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 31% · 17
  • 3–10 min 52% · 28
  • 10–30 min 17% · 9
  • 30+ min 0% · 0

On-time by weekday

  • 13% M n=8
  • 0% T n=7
  • 14% W n=7
  • 25% T n=8
  • 0% F n=8
  • 75% S n=8
  • 88% S n=8

Stops and timetable

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

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