Os 25054 25054 Chrudim – Moravany

View line Os 25054

Chrudim 18:22 → Moravany 18:53 Daily 0 h 31 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 18:22 from Chrudim · Mon 9 Nov

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

Last 30 days

Arrival delay at Moravany, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 17 Aug Max en route +8 min · last fix heading to — +3 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 98% · 53
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=8
  • 100% 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, 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:22on time +1 min
18:25 / 18:26≈ on time ≈ +1 min
18:34≈ on time ≈ on time
18:36≈ on time ≈ on time
18:37≈ on time ≈ on time
18:42 / 18:45≈ on time ≈ on time
18:48≈ on time ≈ on time
18:53on time on time

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 NovMoravany 18:54No data—
Sat 7 NovMoravany 18:54No data—
Fri 6 NovMoravany 18:54No data—
Thu 5 NovMoravany 18:54No data—
Wed 4 NovMoravany 18:54No data—
Tue 3 NovMoravany 18:54No data—
Mon 2 NovMoravany 18:54No data—
Sun 1 NovMoravany 18:54No data—
Sat 31 OctMoravany 18:54No data—
Fri 30 OctMoravany 18:54No data—
Thu 29 OctMoravany 18:54No data—
Wed 28 OctMoravany 18:54No data—
Tue 27 OctMoravany 18:55No data—
Mon 26 OctMoravany 18:54No data—
Sun 25 OctMoravany 18:54No data—
Sat 24 OctMoravany 18:55No data—
Fri 23 OctMoravany 18:55No data—
Thu 22 OctMoravany 18:54No data—
Wed 21 OctMoravany 18:54No data—
Tue 20 OctMoravany 18:55No data—
Mon 19 OctMoravany 18:54No data—
Sun 18 OctMoravany 18:54No data—
Sat 17 OctMoravany 18:54No data—
Fri 16 OctMoravany 18:54No data—
Thu 15 OctMoravany 18:54No data—
Wed 14 OctMoravany 18:54No data—
Tue 13 OctMoravany 18:54No data—
Mon 12 OctMoravany 18:55No data—
Sun 11 OctMoravany 18:54No data—
Sat 10 OctMoravany 18:54No data—