Os 16514 16514 Ústí n. L. hl. n. – Most

View line Os 16514

Ústí n. L. hl. n. 13:30 → Most 14:25 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 19 stops RegioJet ÚK a.s.

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 13:30 from Ústí n. L. hl. n. · Mon 16 Nov

Next departure 13:30 tomorrow · Ústí n. L. hl. n.
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
18%
6/34 runs under 3 min
RT coverage: 34 full · 0 partial · 28 no data
Typical delay
+6min
Median at arrival, 90 days
P90
+10min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Most, 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 20 Aug Max en route +26 min · last fix heading to — +26 min
  • Tue 1 Sept Max en route +17 min · last fix heading to — +17 min
  • Mon 7 Sept Max en route +16 min · last fix heading to — +16 min
  • Tue 15 Sept Max en route +10 min · last fix heading to — +10 min
  • Fri 4 Sept Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 18% · 6
  • 3–10 min 68% · 23
  • 10–30 min 15% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=6
  • 0% T n=7
  • 14% W n=7
  • 29% T n=7
  • 14% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
13:30+3 min +7 min
13:32≈ +3 min ≈ +7 min
13:37≈ +3 min ≈ +7 min
13:40≈ +3 min ≈ +7 min
13:43≈ +3 min ≈ +7 min
13:45≈ +4 min ≈ +7 min
13:47≈ +4 min ≈ +7 min
13:50≈ +4 min ≈ +7 min
13:52≈ +4 min ≈ +7 min
13:54 / 13:55≈ +4 min ≈ +7 min
13:57≈ +4 min ≈ +7 min
14:02 / 14:03≈ +5 min ≈ +8 min
14:06≈ +5 min ≈ +8 min
14:08 / 14:09≈ +5 min ≈ +8 min
14:10≈ +5 min ≈ +9 min
14:14≈ +5 min ≈ +9 min
14:16≈ +6 min ≈ +9 min
14:20≈ +6 min ≈ +10 min
14:25+6 min +10 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 NovMost 14:24No data—
Thu 12 NovMost 14:24No data—
Wed 11 NovMost 14:24No data—
Tue 10 NovMost 14:24No data—
Mon 9 NovMost 14:24No data—
Fri 6 NovMost 14:24No data—
Thu 5 NovMost 14:24No data—
Wed 4 NovMost 14:25No data—
Tue 3 NovMost 14:24No data—
Mon 2 NovMost 14:24No data—
Fri 30 OctMost 14:26No data—
Thu 29 OctMost 14:26No data—
Tue 27 OctMost 14:26No data—
Mon 26 OctMost 14:26No data—
Fri 23 OctMost 14:26No data—
Thu 22 OctMost 14:26No data—
Wed 21 OctMost 14:26No data—
Tue 20 OctMost 14:26No data—
Mon 19 OctMost 14:26No data—
Fri 16 OctMost 14:26No data—
Thu 15 OctMost 14:26No data—
Wed 14 OctMost 14:26No data—
Tue 13 OctMost 14:26No data—
Mon 12 OctMost 14:26No data—
Fri 9 OctMost 14:26No data—
Thu 8 OctMost 14:26No data—
Wed 7 OctMost 14:26No data—
Tue 6 OctMost 14:26No data—
Mon 5 Oct— 14:40+1 min+3 min
Fri 2 Oct— 14:43+3 min+3 min