Os 12733 12733 Rudoltice v Čechách – Lanškroun

View line Os 12733

Rudoltice v Čechách 14:43 → Lanškroun 14:49 Mon, Tue, Wed, Thu, Fri 0 h 06 min · 2 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 13 November No data

Next service: today 14:43 from Rudoltice v Čechách · Mon 16 Nov

Next departure 14:43 today · Rudoltice v Čechách
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
35%
8/23 runs under 3 min
RT coverage: 23 full · 0 partial · 28 no data
Typical delay
+5min
Median at arrival, 90 days
P90
+12min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Lanškroun, in minutes. One bar per run.

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

Worst days

  • Fri 18 Sept Max en route +14 min · last fix heading to — +14 min
  • Wed 23 Sept Max en route +13 min · last fix heading to — +13 min
  • Thu 17 Sept Max en route +12 min · last fix heading to — +12 min
  • Tue 15 Sept Max en route +11 min · last fix heading to — +11 min
  • Fri 25 Sept Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 35% · 8
  • 3–10 min 48% · 11
  • 10–30 min 17% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 40% T n=5
  • 40% W n=5
  • 40% T n=5
  • 0% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
14:43+5 min +12 min
14:49+5 min +12 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 13 NovLanškroun 14:49No data—
Thu 12 NovLanškroun 14:49No data—
Wed 11 NovLanškroun 14:49No data—
Tue 10 NovLanškroun 14:49No data—
Mon 9 NovLanškroun 14:49No data—
Fri 6 NovLanškroun 14:49No data—
Thu 5 NovLanškroun 14:49No data—
Wed 4 NovLanškroun 14:49No data—
Tue 3 NovLanškroun 14:49No data—
Mon 2 NovLanškroun 14:49No data—
Fri 30 OctLanškroun 14:50No data—
Thu 29 OctLanškroun 14:50No data—
Tue 27 OctLanškroun 14:50No data—
Mon 26 OctLanškroun 14:50No data—
Fri 23 OctLanškroun 14:50No data—
Thu 22 OctLanškroun 14:50No data—
Wed 21 OctLanškroun 14:50No data—
Tue 20 OctLanškroun 14:50No data—
Mon 19 OctLanškroun 14:50No data—
Fri 16 OctLanškroun 14:50No data—
Thu 15 OctLanškroun 14:50No data—
Wed 14 OctLanškroun 14:50No data—
Tue 13 OctLanškroun 14:50No data—
Mon 12 OctLanškroun 14:50No data—
Fri 9 OctLanškroun 14:50No data—
Thu 8 OctLanškroun 14:50No data—
Wed 7 OctLanškroun 14:50No data—
Tue 6 OctLanškroun 14:50No data—
Mon 5 Oct— 15:04+1 min+2 min
Fri 2 Oct— 15:09+6 min+8 min