Os 6170 6170 Litoměřice hor.n. – Lovosice

View line Os 6170

Litoměřice hor.n. 08:44 → Lovosice 08:55 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Monday 16 November No data

Next service: tomorrow 08:44 from Litoměřice hor.n. · Wed 18 Nov

Next departure 08:44 tomorrow · Litoměřice hor.n.
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
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Lovosice, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 6% · 2
  • On time 94% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
08:44on time +1 min
08:46≈ on time ≈ +1 min
08:49≈ on time ≈ +1 min
08:52≈ on time ≈ on time
08:55on time on time

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 NovLovosice 08:54No data—
Fri 13 NovLovosice 08:54No data—
Thu 12 NovLovosice 08:54No data—
Wed 11 NovLovosice 08:54No data—
Tue 10 NovLovosice 08:54No data—
Mon 9 NovLovosice 08:54No data—
Fri 6 NovLovosice 08:54No data—
Thu 5 NovLovosice 08:54No data—
Wed 4 NovLovosice 08:54No data—
Tue 3 NovLovosice 08:54No data—
Mon 2 NovLovosice 08:54No data—
Fri 30 OctLovosice 08:56No data—
Thu 29 OctLovosice 08:56No data—
Tue 27 OctLovosice 08:56No data—
Mon 26 OctLovosice 08:56No data—
Fri 23 OctLovosice 08:57No data—
Thu 22 OctLovosice 08:57No data—
Wed 21 OctLovosice 08:56No data—
Tue 20 OctLovosice 08:56No data—
Mon 19 OctLovosice 08:56No data—
Fri 16 OctLovosice 08:57No data—
Thu 15 OctLovosice 08:57No data—
Wed 14 OctLovosice 08:56No data—
Tue 13 OctLovosice 08:56No data—
Mon 12 OctLovosice 08:56No data—
Fri 9 OctLovosice 08:56No data—
Thu 8 OctLovosice 08:56No data—
Wed 7 OctLovosice 08:56No data—
Tue 6 OctLovosice 08:56No data—
Mon 5 Oct— 09:090 min+2 min