Os 6170 6170 Litoměřice hor.n. – Lovosice
Alerts for train 6170
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 6170.
✓ Today’s run finished
Today, last fix heading to Lovosice at 08:54 No data
- Litoměřice hor.n.08:44
- Litoměřice Cihelna08:46
- Žalhostice08:49
- Lovosice závod08:52
- Lovosice08:55
Next service: tomorrow 08:44 from Litoměřice hor.n. · Thu 5 Nov
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
Worst days
- Mon 17 Aug Max en route +5 min · last fix heading to — +3 min
- Mon 10 Aug Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
41 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 5% · 2
- On time 90% · 37
- 3–10 min 5% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 100% T n=8
- 100% W n=8
- 100% T n=8
- 100% F n=9
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 41 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 08:44 | on time | +1 min | |
| 08:46 | ≈ on time | ≈ +1 min | |
| 08:49 | ≈ on time | ≈ +1 min | |
| 08:52 | ≈ on time | ≈ on time | |
| 08:55 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Lovosice 08:54 | No data | — |
| Tue 3 Nov | Lovosice 08:54 | No data | — |
| Mon 2 Nov | Lovosice 08:54 | No data | — |
| Fri 30 Oct | Lovosice 08:56 | No data | — |
| Thu 29 Oct | Lovosice 08:56 | No data | — |
| Tue 27 Oct | Lovosice 08:56 | No data | — |
| Mon 26 Oct | Lovosice 08:56 | No data | — |
| Fri 23 Oct | Lovosice 08:57 | No data | — |
| Thu 22 Oct | Lovosice 08:57 | No data | — |
| Wed 21 Oct | Lovosice 08:56 | No data | — |
| Tue 20 Oct | Lovosice 08:56 | No data | — |
| Mon 19 Oct | Lovosice 08:56 | No data | — |
| Fri 16 Oct | Lovosice 08:57 | No data | — |
| Thu 15 Oct | Lovosice 08:57 | No data | — |
| Wed 14 Oct | Lovosice 08:56 | No data | — |
| Tue 13 Oct | Lovosice 08:56 | No data | — |
| Mon 12 Oct | Lovosice 08:56 | No data | — |
| Fri 9 Oct | Lovosice 08:56 | No data | — |
| Thu 8 Oct | Lovosice 08:56 | No data | — |
| Wed 7 Oct | Lovosice 08:56 | No data | — |
| Tue 6 Oct | Lovosice 08:56 | No data | — |
| Mon 5 Oct | — 09:09 | 0 min | +2 min |
| Fri 2 Oct | — 09:08 | −1 min | — |
| Thu 1 Oct | — 09:10 | +2 min | +3 min |
| Wed 30 Sept | — 09:07 | −1 min | — |
| Tue 29 Sept | — 09:08 | 0 min | +1 min |
| Fri 25 Sept | — 09:08 | 0 min | — |
| Thu 24 Sept | — 09:09 | 0 min | — |
| Wed 23 Sept | — 09:08 | −1 min | — |
| Tue 22 Sept | — 09:23 | −6 min | — |