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

View line Os 5645

Týniště nad Orlicí 05:33 → Choceň 05:58 Tue, Sat, Sun 0 h 25 min · 7 stops České dráhy, a.s.

It does not run today

Last recorded run: Tuesday 17 November No data

Next service: tomorrow 05:33 from Týniště nad Orlicí · Sat 21 Nov

Next departure 05:33 tomorrow · Týniště nad Orlicí
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 14 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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:33on time on time
05:37 / 05:38≈ on time ≈ on time
05:40 / 05:41≈ on time ≈ on time
05:45≈ on time ≈ on time
05:48 / 05:49≈ on time ≈ on time
05:51≈ on time ≈ on time
05:58on 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
Tue 17 NovChoceň 06:00No data—
Sun 15 NovChoceň 05:59No data—
Sat 14 NovChoceň 05:59No data—
Sun 8 NovChoceň 05:59No data—
Sat 7 NovChoceň 05:59No data—
Sun 1 NovChoceň 05:59No data—
Sat 31 OctChoceň 05:59No data—
Wed 28 OctChoceň 06:00No data—
Sun 25 OctChoceň 05:59No data—
Sat 24 OctChoceň 05:59No data—
Sun 18 OctChoceň 05:59No data—
Sat 17 OctChoceň 05:59No data—
Sun 11 OctChoceň 05:59No data—
Sat 10 OctChoceň 05:59No data—
Sun 4 Oct— 06:130 min—
Sat 3 Oct— 06:130 min—
Mon 28 Sept— 06:12−1 min—
Sun 27 Sept— 06:130 min—
Sat 26 Sept— 06:11−1 min—
Sun 20 Sept— 06:11−1 min—
Sat 19 Sept— 06:14+1 min+2 min
Sun 13 Sept— 06:120 min+2 min
Sat 12 Sept— 06:130 min—
Sun 6 Sept— 06:11−1 min—
Sat 5 Sept— 06:130 min+2 min
Sun 30 Aug— 06:11−1 min+1 min
Sat 29 Aug— 06:120 min+2 min
Sun 23 Aug— 06:11−1 min—
Sat 22 Aug— 06:11−1 min—