Os 15063 15063 Vysoké Mýto – Choceň

View line Os 15063

Vysoké Mýto 05:41 → Choceň 05:50 Mon, Tue, Wed, Thu, Fri 0 h 09 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Choceň at 05:49 No data

  1. Vysoké Mýto05:41
  2. Slatina u Vysokého Mýta05:45
  3. Dvořisko05:47
  4. Choceň05:50

Next service: tomorrow 05:41 from Vysoké Mýto · Fri 6 Nov

Next departure 05:41 tomorrow · Vysoké Mýto
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
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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 Choceň, 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

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

  • Early 0% · 0
  • On time 100% · 40
  • 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=8
  • 100% 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, 40 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
05:41on time +2 min
05:45≈ on time ≈ +1 min
05:47≈ on time ≈ +1 min
05:50on 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
Thu 5 NovChoceň 05:49No data—
Wed 4 NovChoceň 05:49No data—
Tue 3 NovChoceň 05:50No data—
Mon 2 NovChoceň 05:49No data—
Fri 30 OctChoceň 05:51No data—
Thu 29 OctChoceň 05:51No data—
Tue 27 OctChoceň 05:51No data—
Mon 26 OctChoceň 05:51No data—
Fri 23 OctChoceň 05:51No data—
Thu 22 OctChoceň 05:51No data—
Wed 21 OctChoceň 05:51No data—
Tue 20 OctChoceň 05:51No data—
Mon 19 OctChoceň 05:51No data—
Fri 16 OctChoceň 05:51No data—
Thu 15 OctChoceň 05:51No data—
Wed 14 OctChoceň 05:51No data—
Tue 13 OctChoceň 05:51No data—
Mon 12 OctChoceň 05:51No data—
Fri 9 OctChoceň 05:51No data—
Thu 8 OctChoceň 05:51No data—
Wed 7 OctChoceň 05:51No data—
Tue 6 OctChoceň 05:52No data—
Mon 5 Oct— 06:040 min—
Fri 2 Oct— 06:040 min—
Thu 1 Oct— 06:040 min—
Wed 30 Sept— 06:040 min+2 min
Tue 29 Sept— 06:040 min—
Fri 25 Sept— 06:040 min—
Thu 24 Sept— 06:040 min—
Wed 23 Sept— 06:05+1 min+2 min