Os 5643 5643 Týniště nad Orlicí – Choceň

View line Os 5643

Týniště nad Orlicí 05:32 → Choceň 05:54 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 7 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Týniště nad Orlicí05:32
  2. Žďár nad Orlicí05:36
  3. Borohrádek05:39
  4. Čermná nad Orlicí05:44
  5. Plchůvky05:47
  6. Újezd u Chocně05:48
  7. Choceň05:54

Next service: Monday 05:32 from Týniště nad Orlicí · Mon 9 Nov

Next departure 05:32 Monday · Týniště nad Orlicí
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 · 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 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 (7 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:32on time on time
05:36 / 05:37≈ on time ≈ on time
05:39 / 05:40≈ on time ≈ on time
05:44≈ on time ≈ +1 min
05:47≈ on time ≈ +1 min
05:48≈ on time ≈ +1 min
05:54on 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 NovChoceň 05:54No data—
Thu 5 NovChoceň 05:54No data—
Wed 4 NovChoceň 05:54No data—
Tue 3 NovChoceň 05:55No data—
Mon 2 NovChoceň 05:54No data—
Fri 30 OctChoceň 05:55No data—
Thu 29 OctChoceň 05:55No data—
Tue 27 OctChoceň 05:55No data—
Mon 26 OctChoceň 05:55No data—
Fri 23 OctChoceň 05:55No data—
Thu 22 OctChoceň 05:55No data—
Wed 21 OctChoceň 05:55No data—
Tue 20 OctChoceň 05:55No data—
Mon 19 OctChoceň 05:55No data—
Fri 16 OctChoceň 05:55No data—
Thu 15 OctChoceň 05:55No data—
Wed 14 OctChoceň 05:55No data—
Tue 13 OctChoceň 05:55No data—
Mon 12 OctChoceň 05:55No data—
Fri 9 OctChoceň 05:55No data—
Thu 8 OctChoceň 05:55No data—
Wed 7 OctChoceň 05:55No data—
Tue 6 OctChoceň 05:56No data—
Mon 5 Oct— 06:090 min+2 min
Fri 2 Oct— 06:090 min+1 min
Thu 1 Oct— 06:07−1 min—
Wed 30 Sept— 06:080 min—
Tue 29 Sept— 06:09+1 min+2 min
Fri 25 Sept— 06:080 min—
Thu 24 Sept— 06:080 min—