Os 25046 25046 Chrudim – Moravany

View line Os 25046

Chrudim 10:22 → Moravany 10:53 Daily 0 h 31 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Moravany at 10:54 No data

  1. Chrudim10:22
  2. Chrudim město10:25
  3. Tuněchody10:34
  4. Vejvanovice10:37
  5. Hrochův Týnec10:42
  6. Bořice10:48
  7. Moravany10:53

Next service: tomorrow 10:22 from Chrudim · Wed 11 Nov

Next departure 10:22 tomorrow · Chrudim
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
100%
54/54 runs under 3 min
RT coverage: 54 full · 0 partial · 36 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

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 100% · 54
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=7
  • 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, 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
10:22on time on time
10:25 / 10:26≈ on time ≈ on time
10:34≈ on time ≈ on time
10:36≈ on time ≈ on time
10:37≈ on time ≈ on time
10:42 / 10:45≈ on time ≈ on time
10:48≈ on time ≈ on time
10: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
Tue 10 NovMoravany 10:54No data—
Mon 9 NovMoravany 10:54No data—
Sun 8 NovMoravany 10:54No data—
Sat 7 NovMoravany 10:54No data—
Fri 6 NovMoravany 10:54No data—
Thu 5 NovMoravany 10:54No data—
Wed 4 NovMoravany 10:54No data—
Tue 3 NovMoravany 10:54No data—
Mon 2 NovMoravany 10:54No data—
Sun 1 NovMoravany 10:54No data—
Sat 31 OctMoravany 10:54No data—
Fri 30 OctMoravany 10:54No data—
Thu 29 OctMoravany 10:54No data—
Wed 28 OctMoravany 10:54No data—
Tue 27 OctMoravany 10:54No data—
Mon 26 OctMoravany 10:54No data—
Sun 25 OctMoravany 10:54No data—
Sat 24 OctMoravany 10:54No data—
Fri 23 OctMoravany 10:54No data—
Thu 22 OctMoravany 10:54No data—
Wed 21 OctMoravany 10:54No data—
Tue 20 OctMoravany 10:54No data—
Mon 19 OctMoravany 10:54No data—
Sun 18 OctMoravany 10:54No data—
Sat 17 OctMoravany 10:54No data—
Fri 16 OctMoravany 10:54No data—
Thu 15 OctMoravany 10:54No data—
Wed 14 OctMoravany 10:54No data—
Tue 13 OctMoravany 10:54No data—
Mon 12 OctMoravany 10:54No data—