Os 15000 15000 Choceň – Litomyšl

View line Os 15000

Choceň 04:56 → Litomyšl 05:35 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Litomyšl at 05:34 No data

  1. Choceň04:56
  2. Slatina u Vysokého Mýta05:01
  3. Vysoké Mýto město05:10
  4. Cerekvice nad Loučnou05:20
  5. Řídký05:26
  6. Litomyšl-Nedošín05:29
  7. Litomyšl05:35

Next service: tomorrow 04:56 from Choceň · Wed 11 Nov

Next departure 04:56 tomorrow · Choceň
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
95%
35/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Litomyšl, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 23 Sept Max en route +5 min · last fix heading to — +4 min
  • Fri 18 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 38% · 14
  • On time 57% · 21
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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:56on time +3 min
04:58≈ on time ≈ +3 min
05:01≈ on time ≈ +2 min
05:06 / 05:07≈ on time ≈ +2 min
05:10 / 05:11≈ on time ≈ +1 min
05:15≈ on time ≈ +1 min
05:18≈ 1 min early ≈ +1 min
05:20 / 05:21≈ 1 min early ≈ +1 min
05:23≈ 1 min early ≈ +1 min
05:26≈ 1 min early ≈ +1 min
05:27≈ 1 min early ≈ +1 min
05:29≈ 1 min early ≈ +1 min
05:31≈ 1 min early ≈ +1 min
05:351 min early 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 NovLitomyšl 05:34No data—
Mon 9 NovLitomyšl 05:34No data—
Fri 6 NovLitomyšl 05:34No data—
Thu 5 NovLitomyšl 05:34No data—
Wed 4 NovLitomyšl 05:34No data—
Tue 3 NovLitomyšl 05:35No data—
Mon 2 NovLitomyšl 05:34No data—
Fri 30 OctLitomyšl 05:36No data—
Thu 29 OctLitomyšl 05:36No data—
Tue 27 OctLitomyšl 05:36No data—
Mon 26 OctLitomyšl 05:36No data—
Fri 23 OctLitomyšl 05:36No data—
Thu 22 OctLitomyšl 05:36No data—
Wed 21 OctLitomyšl 05:36No data—
Tue 20 OctLitomyšl 05:36No data—
Mon 19 OctLitomyšl 05:36No data—
Fri 16 OctLitomyšl 05:36No data—
Thu 15 OctLitomyšl 05:36No data—
Wed 14 OctLitomyšl 05:36No data—
Tue 13 OctLitomyšl 05:36No data—
Mon 12 OctLitomyšl 05:36No data—
Fri 9 OctLitomyšl 05:36No data—
Thu 8 OctLitomyšl 05:36No data—
Wed 7 OctLitomyšl 05:36No data—
Tue 6 OctLitomyšl 05:37No data—
Mon 5 Oct— 05:500 min+3 min
Fri 2 Oct— 05:47−2 min+2 min
Thu 1 Oct— 05:48−1 min+2 min
Wed 30 Sept— 05:47−2 min—
Tue 29 Sept— 05:47−2 min+1 min