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

View line Os 16508

Ústí n. L. hl. n. 08:30 → Most 09:25 Daily 0 h 55 min · 19 stops RegioJet ÚK a.s.

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 08:30 from Ústí n. L. hl. n. · Sun 8 Nov

Next departure 08:30 today · Ústí n. L. hl. n.
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
68%
38/56 runs under 3 min
RT coverage: 56 full · 0 partial · 33 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+6min
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

  • Sat 29 Aug Max en route +17 min · last fix heading to — +14 min
  • Wed 30 Sept Max en route +13 min · last fix heading to — +13 min
  • Fri 4 Sept Max en route +11 min · last fix heading to — +9 min
  • Thu 20 Aug Max en route +11 min · last fix heading to — +9 min
  • Wed 9 Sept Max en route +9 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 38
  • 3–10 min 29% · 16
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 38% T n=8
  • 50% W n=8
  • 63% T n=8
  • 63% F n=8
  • 75% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 56 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
08:30on time +3 min
08:32≈ on time ≈ +3 min
08:37≈ on time ≈ +3 min
08:40≈ +1 min ≈ +3 min
08:43≈ +1 min ≈ +4 min
08:45≈ +1 min ≈ +4 min
08:47≈ +1 min ≈ +4 min
08:50≈ +1 min ≈ +4 min
08:52≈ +1 min ≈ +4 min
08:54 / 08:55≈ +1 min ≈ +4 min
08:57≈ +1 min ≈ +4 min
09:02 / 09:03≈ +1 min ≈ +5 min
09:06≈ +1 min ≈ +5 min
09:08 / 09:09≈ +1 min ≈ +5 min
09:10≈ +1 min ≈ +5 min
09:14≈ +1 min ≈ +6 min
09:16≈ +1 min ≈ +6 min
09:20≈ +1 min ≈ +6 min
09:25+1 min +6 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
Sat 7 NovMost 09:25No data—
Fri 6 NovBílina 09:14No data—
Thu 5 NovBílina 09:14No data—
Wed 4 NovBílina 09:14No data—
Tue 3 NovBílina 09:14No data—
Mon 2 NovBílina 09:14No data—
Sun 1 NovMost 09:26No data—
Sat 31 OctMost 09:26No data—
Fri 30 OctBílina 09:15No data—
Thu 29 OctBílina 09:15No data—
Wed 28 OctMost 09:26No data—
Tue 27 OctBílina 09:15No data—
Mon 26 OctBílina 09:15No data—
Sun 25 OctMost 09:26No data—
Sat 24 OctMost 09:26No data—
Fri 23 OctBílina 09:15No data—
Thu 22 OctBílina 09:16No data—
Wed 21 OctBílina 09:15No data—
Tue 20 OctBílina 09:15No data—
Mon 19 OctBílina 09:15No data—
Sun 18 OctMost 09:26No data—
Sat 17 OctMost 09:26No data—
Fri 16 OctBílina 09:16No data—
Thu 15 OctBílina 09:16No data—
Wed 14 OctBílina 09:15No data—
Tue 13 OctBílina 09:15No data—
Mon 12 OctBílina 09:15No data—
Sun 11 OctMost 09:26No data—
Sat 10 OctMost 09:26No data—
Fri 9 OctBílina 09:15No data—