Os 16522 16522 Ústí n. L. hl. n. – Bílina

View line Os 16522

Ústí n. L. hl. n. 17:30 → Bílina 18:14 Mon, Tue, Wed, Thu, Fri 0 h 44 min · 16 stops RegioJet ÚK a.s.

It does not run today

Last recorded run: Friday 6 November No data

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

Next departure 17: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
50%
19/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Bílina, 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 4 Sept Max en route +14 min · last fix heading to — +12 min
  • Wed 2 Sept Max en route +10 min · last fix heading to — +9 min
  • Fri 28 Aug Max en route +12 min · last fix heading to — +9 min
  • Mon 24 Aug Max en route +10 min · last fix heading to — +8 min
  • Wed 19 Aug Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 50% · 19
  • 3–10 min 47% · 18
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 50% T n=8
  • 13% W n=8
  • 63% T n=8
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

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