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

View line Os 12731

Česká Třebová 14:04 → Lanškroun 14:22 Daily 0 h 18 min · 4 stops České dráhy, a.s.

Running now · updated 14:15

Between Třebovice v Čechách and Rudoltice v Čechách No data

Estimated arrival at Lanškroun 14:22 · 76 km/h

  1. Česká Třebová14:04
  2. Třebovice v Čechách14:09
  3. Rudoltice v Čechách14:15
  4. Lanškroun14:22
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
38%
21/55 runs under 3 min
RT coverage: 55 full · 0 partial · 31 no data
Typical delay
+4min
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

  • Wed 12 Aug Max en route +18 min · last fix heading to — +16 min
  • Sun 23 Aug Max en route +17 min · last fix heading to — +14 min
  • Wed 19 Aug Max en route +16 min · last fix heading to — +14 min
  • Fri 18 Sept Max en route +13 min · last fix heading to — +13 min
  • Fri 11 Sept Max en route +13 min · last fix heading to — +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 38% · 21
  • 3–10 min 45% · 25
  • 10–30 min 16% · 9
  • 30+ min 0% · 0

On-time by weekday

  • 38% M n=8
  • 63% T n=8
  • 38% W n=8
  • 43% T n=7
  • 17% F n=6
  • 33% S n=9
  • 33% S n=9

Stops and timetable

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

Last 90 days, 55 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
14:04+3 min +10 minPassed
14:09≈ +3 min ≈ +10 minPassed
14:15 / 14:16≈ +4 min ≈ +11 minNext
14:22+4 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
Thu 5 NovRudoltice v Čechách 14:14Partial coverageNo data—
Wed 4 NovLanškroun 14:24No data—
Tue 3 NovLanškroun 14:24No data—
Mon 2 NovLanškroun 14:24No data—
Sun 1 NovLanškroun 14:24No data—
Sat 31 OctLanškroun 14:24No data—
Fri 30 OctLanškroun 14:24No data—
Thu 29 OctLanškroun 14:24No data—
Wed 28 OctLanškroun 14:24No data—
Tue 27 OctLanškroun 14:24No data—
Mon 26 OctLanškroun 14:24No data—
Sun 25 OctLanškroun 14:24No data—
Sat 24 OctLanškroun 14:24No data—
Fri 23 OctLanškroun 14:24No data—
Thu 22 OctLanškroun 14:24No data—
Wed 21 OctLanškroun 14:24No data—
Tue 20 OctLanškroun 14:24No data—
Mon 19 OctLanškroun 14:24No data—
Sun 18 OctLanškroun 14:24No data—
Sat 17 OctLanškroun 14:24No data—
Fri 16 OctLanškroun 14:24No data—
Thu 15 OctLanškroun 14:24No data—
Wed 14 OctLanškroun 14:24No data—
Tue 13 OctLanškroun 14:24No data—
Mon 12 OctLanškroun 14:24No data—
Sun 11 OctLanškroun 14:24No data—
Sat 10 OctLanškroun 14:24No data—
Fri 9 OctLanškroun 14:24No data—
Thu 8 OctLanškroun 14:24No data—
Wed 7 OctLanškroun 14:24No data—