Os 25049 25049 Moravany – Chrudim

View line Os 25049

Moravany 13:04 → Chrudim 13:35 Daily 0 h 31 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 13:04 from Moravany · Thu 5 Nov

Next departure 13:04 today · Moravany
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
59%
35/59 runs under 3 min
RT coverage: 59 full · 0 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+12min
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

  • Fri 4 Sept Max en route +22 min · last fix heading to — +21 min
  • Fri 28 Aug Max en route +21 min · last fix heading to — +18 min
  • Sat 15 Aug Max en route +24 min · last fix heading to — +18 min
  • Fri 2 Oct Max en route +15 min · last fix heading to — +12 min
  • Sun 20 Sept Max en route +18 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 59% · 35
  • 3–10 min 25% · 15
  • 10–30 min 15% · 9
  • 30+ min 0% · 0

On-time by weekday

  • 44% M n=9
  • 75% T n=8
  • 88% W n=8
  • 50% T n=8
  • 38% F n=8
  • 56% S n=9
  • 67% S n=9

Stops and timetable

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

Last 90 days, 59 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
13:04+4 min +15 min
13:08≈ +4 min ≈ +15 min
13:12 / 13:14≈ +3 min ≈ +15 min
13:18≈ +3 min ≈ +14 min
13:20≈ +2 min ≈ +14 min
13:22≈ +2 min ≈ +13 min
13:29 / 13:32≈ +2 min ≈ +13 min
13:35+1 min +12 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
Wed 4 NovChrudim 13:35No data—
Tue 3 NovChrudim 13:34No data—
Mon 2 NovChrudim 13:34No data—
Sun 1 NovChrudim 13:36No data—
Sat 31 OctChrudim 13:36No data—
Fri 30 OctChrudim 13:36No data—
Thu 29 OctChrudim 13:36No data—
Wed 28 OctChrudim 13:36No data—
Tue 27 OctChrudim 13:36No data—
Mon 26 OctChrudim 13:36No data—
Sun 25 OctChrudim 13:36No data—
Sat 24 OctChrudim 13:36No data—
Fri 23 OctChrudim 13:36No data—
Thu 22 OctChrudim 13:36No data—
Wed 21 OctChrudim 13:36No data—
Tue 20 OctChrudim 13:36No data—
Mon 19 OctChrudim 13:36No data—
Sun 18 OctChrudim 13:36No data—
Sat 17 OctChrudim 13:36No data—
Fri 16 OctChrudim 13:36No data—
Thu 15 OctChrudim 13:36No data—
Wed 14 OctChrudim 13:36No data—
Tue 13 OctChrudim 13:36No data—
Mon 12 OctChrudim 13:36No data—
Sun 11 OctChrudim 13:36No data—
Sat 10 OctChrudim 13:36No data—
Fri 9 OctChrudim 13:36No data—
Thu 8 OctChrudim 13:36No data—
Wed 7 OctChrudim 13:36No data—
Tue 6 OctChrudim 13:36No data—