Os 25041 25041 Holice – Chrudim

View line Os 25041

Holice 04:47 → Chrudim 05:40 Daily 0 h 53 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Chrudim at 05:39 No data

  1. Holice04:47
  2. Platěnice04:56
  3. Moravany04:59
  4. Hrochův Týnec05:19
  5. Úhřetice05:26
  6. Tuněchody05:28
  7. Chrudim05:40

Next service: tomorrow 04:47 from Holice · Sat 7 Nov

Next departure 04:47 tomorrow · Holice
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
88%
51/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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

  • Thu 10 Sept Max en route +12 min · last fix heading to — +12 min
  • Mon 7 Sept Max en route +11 min · last fix heading to — +9 min
  • Fri 4 Sept Max en route +5 min · last fix heading to — +5 min
  • Thu 3 Sept Max en route +6 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 51
  • 3–10 min 10% · 6
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 100% T n=8
  • 88% W n=8
  • 75% T n=8
  • 75% F n=8
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
04:47on time on time
04:53≈ on time ≈ +1 min
04:56≈ on time ≈ +1 min
04:59 / 05:11≈ on time ≈ +1 min
05:15≈ on time ≈ +2 min
05:19 / 05:20≈ on time ≈ +2 min
05:24≈ on time ≈ +2 min
05:26≈ on time ≈ +2 min
05:28≈ on time ≈ +3 min
05:35 / 05:37≈ on time ≈ +3 min
05:40on time +3 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
Fri 6 NovChrudim 05:39No data—
Thu 5 NovChrudim 05:39No data—
Wed 4 NovChrudim 05:39No data—
Tue 3 NovChrudim 05:40No data—
Mon 2 NovChrudim 05:39No data—
Sun 1 NovMoravany 05:00No data—
Sat 31 OctMoravany 05:00No data—
Fri 30 OctChrudim 05:41No data—
Thu 29 OctChrudim 05:41No data—
Wed 28 OctMoravany 05:01No data—
Tue 27 OctChrudim 05:41No data—
Mon 26 OctChrudim 05:41No data—
Sun 25 OctMoravany 05:00No data—
Sat 24 OctMoravany 05:00No data—
Fri 23 OctChrudim 05:41No data—
Thu 22 OctChrudim 05:41No data—
Wed 21 OctChrudim 05:41No data—
Tue 20 OctChrudim 05:41No data—
Mon 19 OctChrudim 05:41No data—
Sun 18 OctMoravany 05:00No data—
Sat 17 OctMoravany 05:00No data—
Fri 16 OctChrudim 05:41No data—
Thu 15 OctChrudim 05:41No data—
Wed 14 OctChrudim 05:41No data—
Tue 13 OctChrudim 05:41No data—
Mon 12 OctChrudim 05:41No data—
Sun 11 OctMoravany 05:00No data—
Sat 10 OctMoravany 05:00No data—
Fri 9 OctChrudim 05:41No data—
Thu 8 OctChrudim 05:41No data—