Os 5161 5161 Týniště nad Orlicí – Vamberk

View line Os 5161

Týniště nad Orlicí 05:08 → Vamberk 05:40 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 8 stops České dráhy, a.s.

Running now · updated 05:26

Position estimated from the timetable

Between Kostelec nad Orlicí and Doudleby nad Orlicí No data

Estimated arrival at Vamberk 05:40 · 7 km/h

  1. Týniště nad Orlicí05:08
  2. Lípa nad Orlicí05:11
  3. Čestice05:14
  4. Kostelec nad Orlicí město05:20
  5. Kostelec nad Orlicí05:22
  6. Doudleby nad Orlicí05:26
  7. Vamberk05:40
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 31 full · 0 partial · 30 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 Vamberk, 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 +4 min · last fix heading to — +4 min
  • Tue 22 Sept Max en route +14 min · last fix heading to — +4 min
  • Wed 23 Sept Max en route +14 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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 10Today
05:08on time on timePassed
05:11≈ on time ≈ on timePassed
05:14≈ on time ≈ +1 minPassed
05:17 / 05:18≈ on time ≈ +1 minPassed
05:20 / 05:21≈ on time ≈ +1 minPassed
05:22≈ on time ≈ +1 minPassed
05:26 / 05:36≈ on time ≈ +1 minNext
05:40on 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
Wed 18 NovDoudleby nad Orlicí 05:24Partial coverageNo data—
Mon 16 NovVamberk 05:40No data—
Fri 13 NovVamberk 05:39No data—
Thu 12 NovVamberk 05:39No data—
Wed 11 NovVamberk 05:39No data—
Tue 10 NovVamberk 05:39No data—
Mon 9 NovVamberk 05:39No data—
Fri 6 NovVamberk 05:39No data—
Thu 5 NovVamberk 05:39No data—
Wed 4 NovVamberk 05:39No data—
Tue 3 NovVamberk 05:40No data—
Mon 2 NovVamberk 05:39No data—
Fri 30 OctVamberk 05:41No data—
Thu 29 OctVamberk 05:41No data—
Tue 27 OctVamberk 05:41No data—
Mon 26 OctVamberk 05:41No data—
Fri 23 OctVamberk 05:41No data—
Thu 22 OctVamberk 05:41No data—
Wed 21 OctVamberk 05:41No data—
Tue 20 OctVamberk 05:41No data—
Mon 19 OctVamberk 05:41No data—
Fri 16 OctVamberk 05:41No data—
Thu 15 OctVamberk 05:41No data—
Wed 14 OctVamberk 05:41No data—
Tue 13 OctVamberk 05:41No data—
Mon 12 OctVamberk 05:41No data—
Fri 9 OctVamberk 05:41No data—
Thu 8 OctVamberk 05:41No data—
Wed 7 OctVamberk 05:41No data—
Tue 6 OctVamberk 05:42No data—