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

View line Os 16504

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

✓ Today’s run finished

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

  1. Ústí n. L. hl. n.06:30
  2. Koštov06:40
  3. Brozánky06:47
  4. Úpořiny06:54
  5. Hostomice nad Bílinou07:06
  6. Bílina07:14
  7. Most07:25

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

Next departure 06:30 tomorrow · Ústí n. L. hl. n.
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
39%
23/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+11min
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 +41 min · last fix heading to — +38 min
  • Fri 25 Sept Max en route +34 min · last fix heading to — +34 min
  • Thu 24 Sept Max en route +14 min · last fix heading to — +14 min
  • Wed 30 Sept Max en route +13 min · last fix heading to — +13 min
  • Thu 3 Sept Max en route +12 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 39% · 23
  • 3–10 min 49% · 29
  • 10–30 min 8% · 5
  • 30+ min 3% · 2

On-time by weekday

  • 33% M n=9
  • 13% T n=8
  • 25% W n=8
  • 13% T n=8
  • 25% F n=8
  • 67% S n=9
  • 89% S n=9

Stops and timetable

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

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