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

View line Os 16506

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

✓ Today’s run finished

Today, last fix heading to Most at 08:24 No data

  1. Ústí n. L. hl. n.07:30
  2. Koštov07:40
  3. Brozánky07:47
  4. Úpořiny07:54
  5. Hostomice nad Bílinou08:06
  6. Bílina08:14
  7. Most08:25

Next service: tomorrow 07:30 from Ústí n. L. hl. n. · Fri 6 Nov

Next departure 07:30 tomorrow · Ústí n. L. hl. n.
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
20%
8/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
+7min
Median at arrival, 90 days
P90
+12min
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

  • Fri 25 Sept Max en route +50 min · last fix heading to — +46 min
  • Mon 7 Sept Max en route +17 min · last fix heading to — +17 min
  • Thu 13 Aug Max en route +15 min · last fix heading to — +15 min
  • Thu 1 Oct Max en route +15 min · last fix heading to — +14 min
  • Thu 3 Sept Max en route +12 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 20% · 8
  • 3–10 min 55% · 22
  • 10–30 min 23% · 9
  • 30+ min 3% · 1

On-time by weekday

  • 13% M n=8
  • 25% T n=8
  • 25% W n=8
  • 13% 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 (19 stops).

Last 90 days, 40 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
07:30+5 min +9 min
07:32≈ +5 min ≈ +9 min
07:37≈ +5 min ≈ +9 min
07:40≈ +5 min ≈ +9 min
07:43≈ +5 min ≈ +9 min
07:45≈ +5 min ≈ +9 min
07:47≈ +5 min ≈ +9 min
07:50≈ +6 min ≈ +10 min
07:52≈ +6 min ≈ +10 min
07:54 / 07:55≈ +6 min ≈ +10 min
07:57≈ +6 min ≈ +10 min
08:02 / 08:03≈ +6 min ≈ +10 min
08:06≈ +6 min ≈ +11 min
08:08 / 08:09≈ +6 min ≈ +11 min
08:10≈ +6 min ≈ +11 min
08:14≈ +7 min ≈ +11 min
08:16≈ +7 min ≈ +12 min
08:20≈ +7 min ≈ +12 min
08:25+7 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 NovMost 08:24No data—
Wed 4 NovMost 08:24No data—
Tue 3 NovMost 08:24No data—
Mon 2 NovMost 08:24No data—
Fri 30 OctMost 08:26No data—
Thu 29 OctMost 08:26No data—
Tue 27 OctMost 08:26No data—
Mon 26 OctMost 08:26No data—
Fri 23 OctMost 08:27No data—
Thu 22 OctMost 08:27No data—
Wed 21 OctMost 08:26No data—
Tue 20 OctMost 08:26No data—
Mon 19 OctMost 08:26No data—
Fri 16 OctMost 08:26No data—
Thu 15 OctMost 08:26No data—
Wed 14 OctMost 08:26No data—
Tue 13 OctMost 08:26No data—
Mon 12 OctMost 08:26No data—
Fri 9 OctMost 08:26No data—
Thu 8 OctMost 08:26No data—
Wed 7 OctMost 08:26No data—
Tue 6 OctMost 08:26No data—
Mon 5 Oct— 08:50+11 min+11 min
Fri 2 Oct— 08:43+3 min+5 min
Thu 1 Oct— 08:53+14 min+15 min
Wed 30 Sept— 08:43+4 min+5 min
Tue 29 Sept— 08:47+8 min+8 min
Fri 25 Sept— 09:25+46 min+50 min
Thu 24 Sept— 08:45+5 min+9 min
Wed 23 Sept— 08:46+7 min+8 min