Os 15003 15003 Litomyšl – Choceň

View line Os 15003

Litomyšl 05:45 → Choceň 06:26 Mon, Tue, Wed, Thu, Fri 0 h 41 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Choceň at 06:27 No data

  1. Litomyšl05:45
  2. Litomyšl-Nedošín05:48
  3. Řídký05:52
  4. Hrušová06:00
  5. Vysoké Mýto město06:10
  6. Slatina u Vysokého Mýta06:19
  7. Choceň06:26

Next service: Monday 05:45 from Litomyšl · Mon 9 Nov

Next departure 05:45 Monday · Litomyšl
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%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 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 Choceň, 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 24 Sept Max en route +6 min · last fix heading to — +5 min
  • Mon 7 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 88% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% 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 (14 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:45on time +1 min
05:47≈ on time ≈ +1 min
05:48≈ on time ≈ +1 min
05:50≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:56≈ on time ≈ +1 min
05:58 / 05:59≈ on time ≈ on time
06:00≈ on time ≈ on time
06:04≈ on time ≈ on time
06:10 / 06:11≈ on time ≈ +1 min
06:13 / 06:14≈ on time ≈ +1 min
06:19≈ 1 min early ≈ on time
06:22≈ 1 min early ≈ on time
06:261 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
Fri 6 NovChoceň 06:27No data—
Thu 5 NovChoceň 06:27No data—
Wed 4 NovChoceň 06:27No data—
Tue 3 NovChoceň 06:28No data—
Mon 2 NovChoceň 06:27No data—
Fri 30 OctChoceň 06:27No data—
Thu 29 OctChoceň 06:27No data—
Tue 27 OctChoceň 06:27No data—
Mon 26 OctChoceň 06:27No data—
Fri 23 OctChoceň 06:27No data—
Thu 22 OctChoceň 06:27No data—
Wed 21 OctChoceň 06:27No data—
Tue 20 OctChoceň 06:27No data—
Mon 19 OctChoceň 06:27No data—
Fri 16 OctChoceň 06:27No data—
Thu 15 OctChoceň 06:27No data—
Wed 14 OctChoceň 06:27No data—
Tue 13 OctChoceň 06:27No data—
Mon 12 OctChoceň 06:27No data—
Fri 9 OctChoceň 06:27No data—
Thu 8 OctChoceň 06:27No data—
Wed 7 OctChoceň 06:27No data—
Tue 6 OctChoceň 06:28No data—
Mon 5 Oct— 06:40−1 min—
Fri 2 Oct— 06:40−1 min—
Thu 1 Oct— 06:40−1 min—
Wed 30 Sept— 06:39−1 min—
Tue 29 Sept— 06:39−1 min+1 min
Fri 25 Sept— 06:420 min+1 min
Thu 24 Sept— 06:45+5 min+6 min