Os 7140 7140 Letohrad – Ústí nad Orlicí

View line Os 7140

Letohrad 03:59 → Ústí nad Orlicí 04:17 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 7 stops Leo Express Tenders s.r.o.

✓ Today’s run finished

Today, last fix heading to Ústí nad Orlicí at 04:18 No data

  1. Letohrad03:59
  2. Dolní Dobrouč04:03
  3. Hnátnice04:05
  4. Lanšperk04:07
  5. Černovír04:10
  6. Dolní Libchavy04:13
  7. Ústí nad Orlicí04:17

Next service: tomorrow 03:59 from Letohrad · Fri 13 Nov

Next departure 03:59 tomorrow · Letohrad
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 27 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 Ústí nad Orlicí, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
03:59on time +1 min
04:03≈ on time ≈ +1 min
04:05≈ on time ≈ +1 min
04:07 / 04:08≈ on time ≈ +1 min
04:10≈ on time ≈ +1 min
04:13≈ on time ≈ on time
04:17on 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
Thu 12 NovÚstí nad Orlicí 04:18No data—
Wed 11 NovÚstí nad Orlicí 04:18No data—
Tue 10 NovÚstí nad Orlicí 04:18No data—
Mon 9 NovÚstí nad Orlicí 04:18No data—
Fri 6 NovÚstí nad Orlicí 04:18No data—
Thu 5 NovÚstí nad Orlicí 04:18No data—
Wed 4 NovÚstí nad Orlicí 04:18No data—
Tue 3 NovÚstí nad Orlicí 04:18No data—
Mon 2 NovÚstí nad Orlicí 04:18No data—
Fri 30 OctÚstí nad Orlicí 04:18No data—
Thu 29 OctÚstí nad Orlicí 04:18No data—
Tue 27 OctÚstí nad Orlicí 04:18No data—
Mon 26 OctÚstí nad Orlicí 04:18No data—
Fri 23 OctÚstí nad Orlicí 04:18No data—
Thu 22 OctÚstí nad Orlicí 04:18No data—
Wed 21 OctÚstí nad Orlicí 04:18No data—
Tue 20 OctÚstí nad Orlicí 04:18No data—
Mon 19 OctÚstí nad Orlicí 04:18No data—
Fri 16 OctÚstí nad Orlicí 04:18No data—
Thu 15 OctÚstí nad Orlicí 04:18No data—
Wed 14 OctÚstí nad Orlicí 04:18No data—
Tue 13 OctÚstí nad Orlicí 04:18No data—
Mon 12 OctÚstí nad Orlicí 04:18No data—
Fri 9 OctÚstí nad Orlicí 04:18No data—
Thu 8 OctÚstí nad Orlicí 04:18No data—
Wed 7 OctÚstí nad Orlicí 04:18No data—
Tue 6 OctÚstí nad Orlicí 04:18No data—
Mon 5 Oct— 04:310 min—
Fri 2 Oct— 04:310 min—
Thu 1 Oct— 04:30−1 min—