Os 6171 6171 Lovosice – Úštěk

View line Os 6171

Lovosice 13:02 → Úštěk 13:32 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 10 stops České dráhy, a.s.

It does not run today

Last recorded run: Monday 16 November No data

Next service: tomorrow 13:02 from Lovosice · Wed 18 Nov

Next departure 13:02 tomorrow · Lovosice
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
81%
26/32 runs under 3 min
RT coverage: 32 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Úštěk, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 22 Sept Max en route +30 min · last fix heading to — +28 min
  • Fri 2 Oct Max en route +12 min · last fix heading to — +11 min
  • Tue 8 Sept Max en route +5 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min
  • Wed 23 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 26
  • 3–10 min 13% · 4
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 67% T n=6
  • 83% W n=6
  • 100% T n=7
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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:02on time +1 min
13:04≈ on time ≈ +2 min
13:06 / 13:07≈ on time ≈ +2 min
13:09≈ on time ≈ +3 min
13:12 / 13:13≈ on time ≈ +3 min
13:16≈ on time ≈ +3 min
13:19≈ on time ≈ +3 min
13:23≈ on time ≈ +3 min
13:25 / 13:27≈ on time ≈ +3 min
13:32on time +3 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
Mon 16 NovÚštěk 13:33No data—
Fri 13 NovÚštěk 13:33No data—
Thu 12 NovÚštěk 13:34No data—
Wed 11 NovÚštěk 13:33No data—
Tue 10 NovÚštěk 13:33No data—
Mon 9 NovÚštěk 13:33No data—
Fri 6 NovÚštěk 13:33No data—
Thu 5 NovÚštěk 13:33No data—
Wed 4 NovÚštěk 13:34No data—
Tue 3 NovÚštěk 13:33No data—
Mon 2 NovÚštěk 13:33No data—
Fri 30 OctÚštěk 13:33No data—
Thu 29 OctÚštěk 13:33No data—
Tue 27 OctÚštěk 13:33No data—
Mon 26 OctÚštěk 13:33No data—
Fri 23 OctÚštěk 13:33No data—
Thu 22 OctÚštěk 13:33No data—
Wed 21 OctÚštěk 13:33No data—
Tue 20 OctÚštěk 13:33No data—
Mon 19 OctÚštěk 13:33No data—
Fri 16 OctÚštěk 13:33No data—
Thu 15 OctÚštěk 13:33No data—
Wed 14 OctÚštěk 13:33No data—
Tue 13 OctÚštěk 13:33No data—
Mon 12 OctÚštěk 13:33No data—
Fri 9 OctÚštěk 13:33No data—
Thu 8 OctÚštěk 13:33No data—
Wed 7 OctÚštěk 13:33No data—
Tue 6 OctÚštěk 13:33No data—
Mon 5 Oct— 13:49+3 min+3 min