Os 25000 25000 Heřmanův Městec – Přelouč

View line Os 25000

Heřmanův Městec 04:18 → Přelouč 04:38 Mon, Tue, Wed, Thu, Fri 0 h 20 min · 6 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Přelouč at 04:39 No data

  1. Heřmanův Městec04:18
  2. Jeníkovice04:23
  3. Choltice zastávka04:25
  4. Veselí u Přelouče04:29
  5. Valy u Přelouče zastávka04:32
  6. Přelouč04:38

Next service: tomorrow 04:18 from Heřmanův Městec · Wed 11 Nov

Next departure 04:18 tomorrow · Heřmanův Městec
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 25 no data
Typical delay
−1min
Median at arrival, 90 days
P90
−1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Přelouč, 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 28 Aug Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 27% · 8
  • On time 70% · 21
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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:18on time on time
04:23≈ on time ≈ on time
04:25≈ on time ≈ on time
04:29≈ 1 min early ≈ 1 min early
04:32≈ 1 min early ≈ 1 min early
04:381 min early 1 min early

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 NovPřelouč 04:39No data—
Mon 9 NovPřelouč 04:39No data—
Fri 6 NovPřelouč 04:39No data—
Thu 5 NovPřelouč 04:39No data—
Wed 4 NovPřelouč 04:39No data—
Tue 3 NovPřelouč 04:39No data—
Mon 2 NovPřelouč 04:39No data—
Fri 30 OctPřelouč 04:39No data—
Thu 29 OctPřelouč 04:39No data—
Tue 27 OctPřelouč 04:39No data—
Mon 26 OctPřelouč 04:39No data—
Fri 23 OctPřelouč 04:39No data—
Thu 22 OctPřelouč 04:39No data—
Wed 21 OctPřelouč 04:39No data—
Tue 20 OctPřelouč 04:39No data—
Mon 19 OctPřelouč 04:39No data—
Fri 16 OctPřelouč 04:39No data—
Thu 15 OctPřelouč 04:39No data—
Wed 14 OctPřelouč 04:39No data—
Tue 13 OctPřelouč 04:39No data—
Mon 12 OctPřelouč 04:39No data—
Fri 9 OctPřelouč 04:39No data—
Thu 8 OctPřelouč 04:39No data—
Wed 7 OctPřelouč 04:39No data—
Tue 6 OctPřelouč 04:39No data—
Mon 5 Oct— 04:51−1 min—
Fri 2 Oct— 04:51−1 min—
Thu 1 Oct— 04:51−1 min—
Wed 30 Sept— 04:51−1 min—
Tue 29 Sept— 04:51−1 min—