Os 25332 25332 Moravany – Holice

View line Os 25332

Moravany 04:32 → Holice 04:44 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 4 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 04:32 from Moravany · Mon 9 Nov

Next departure 04:32 tomorrow · Moravany
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Holice, 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 7 Sept Max en route +10 min · last fix heading to — +9 min
  • Wed 9 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=8
  • 88% W n=8
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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:32on time +2 min
04:34≈ on time ≈ +2 min
04:37≈ on time ≈ +2 min
04:44on time +1 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 NovHolice 04:44No data—
Thu 5 NovHolice 04:44No data—
Wed 4 NovHolice 04:44No data—
Tue 3 NovHolice 04:45No data—
Mon 2 NovHolice 04:44No data—
Fri 30 OctHolice 04:45No data—
Thu 29 OctHolice 04:45No data—
Tue 27 OctHolice 04:45No data—
Mon 26 OctHolice 04:45No data—
Fri 23 OctHolice 04:45No data—
Thu 22 OctHolice 04:45No data—
Wed 21 OctHolice 04:45No data—
Tue 20 OctHolice 04:45No data—
Mon 19 OctHolice 04:45No data—
Fri 16 OctHolice 04:45No data—
Thu 15 OctHolice 04:45No data—
Wed 14 OctHolice 04:45No data—
Tue 13 OctHolice 04:45No data—
Mon 12 OctHolice 04:45No data—
Fri 9 OctHolice 04:45No data—
Thu 8 OctHolice 04:45No data—
Wed 7 OctHolice 04:45No data—
Tue 6 OctHolice 04:45No data—
Mon 5 Oct— 04:590 min—
Fri 2 Oct— 04:580 min—
Thu 1 Oct— 04:580 min—
Wed 30 Sept— 04:580 min—
Tue 29 Sept— 04:59+1 min+1 min
Fri 25 Sept— 05:00+1 min+2 min
Thu 24 Sept— 04:580 min—