Os 12707 12707 Česká Třebová – Lanškroun

View line Os 12707

Česká Třebová 05:37 → Lanškroun 05:55 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 4 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 05:37 from Česká Třebová · Mon 9 Nov

Full trip card
Next departure 05:37 today · Česká Třebová
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
46%
17/37 runs under 3 min
RT coverage: 37 full · 0 partial · 23 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+8min
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

  • Tue 18 Aug Max en route +12 min · last fix heading to — +12 min
  • Wed 12 Aug Max en route +12 min · last fix heading to — +12 min
  • Wed 16 Sept Max en route +11 min · last fix heading to — +11 min
  • Thu 20 Aug Max en route +10 min · last fix heading to — +9 min
  • Mon 7 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 46% · 17
  • 3–10 min 46% · 17
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 50% T n=6
  • 50% W n=8
  • 50% T n=8
  • 25% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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
Česká Třebová
05:37on time +5 min
Třebovice v Čechách
05:42≈ +1 min ≈ +6 min
Rudoltice v Čechách
05:48 / 05:49≈ +2 min ≈ +7 min
Lanškroun
05:55+3 min +8 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 NovLanškroun 05:54No data—
Thu 5 NovLanškroun 05:57No data—
Wed 4 NovLanškroun 05:57No data—
Tue 3 NovLanškroun 05:55No data—
Mon 2 NovLanškroun 05:57No data—
Fri 30 OctLanškroun 05:57No data—
Thu 29 OctLanškroun 05:57No data—
Tue 27 OctLanškroun 05:57No data—
Mon 26 OctLanškroun 05:57No data—
Fri 23 OctLanškroun 05:57No data—
Thu 22 OctLanškroun 05:57No data—
Wed 21 OctLanškroun 05:57No data—
Tue 20 OctLanškroun 05:57No data—
Mon 19 OctLanškroun 05:57No data—
Fri 16 OctLanškroun 05:57No data—
Thu 15 OctLanškroun 05:57No data—
Wed 14 OctLanškroun 05:57No data—
Tue 13 OctLanškroun 05:57No data—
Mon 12 OctLanškroun 05:57No data—
Fri 9 OctLanškroun 05:57No data—
Thu 8 OctLanškroun 05:57No data—
Wed 7 OctLanškroun 05:57No data—
Tue 6 OctLanškroun 05:57No data—
Mon 5 Oct— 06:14+4 min+4 min
Fri 2 Oct— 06:14+5 min+5 min
Thu 1 Oct— 06:11+2 min+2 min
Wed 30 Sept— 06:12+3 min+4 min
Tue 29 Sept— 06:12+1 min+2 min
Fri 25 Sept— 06:14+4 min+4 min
Thu 24 Sept— 06:090 min+1 min