Os 6173 6173 Lovosice – Litoměřice hor.n.
Alerts for train 6173
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 6173.
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 21:02 from Lovosice · Mon 9 Nov
Last 30 days
Arrival delay at Litoměřice hor.n., in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 30 Sept Max en route +15 min · last fix heading to — +15 min
- Thu 17 Sept Max en route +12 min · last fix heading to — +12 min
- Thu 3 Sept Max en route +12 min · last fix heading to — +12 min
- Wed 12 Aug Max en route +12 min · last fix heading to — +11 min
- Wed 23 Sept Max en route +4 min · last fix heading to — +3 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 87% · 33
- 3–10 min 3% · 1
- 10–30 min 11% · 4
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=8
- 63% W n=8
- 75% T n=8
- 100% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 21:02 | on time | +5 min | |
| 21:04 | ≈ on time | ≈ +5 min | |
| 21:06 / 21:07 | ≈ on time | ≈ +5 min | |
| 21:09 | ≈ on time | ≈ +5 min | |
| 21:12 | on time | +5 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Litoměřice hor.n. 21:13 | No data | — |
| Thu 5 Nov | Litoměřice hor.n. 21:13 | No data | — |
| Wed 4 Nov | Litoměřice hor.n. 21:13 | No data | — |
| Tue 3 Nov | Litoměřice hor.n. 21:13 | No data | — |
| Mon 2 Nov | Litoměřice hor.n. 21:13 | No data | — |
| Fri 30 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Thu 29 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Tue 27 Oct | Litoměřice hor.n. 21:14 | No data | — |
| Mon 26 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Fri 23 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Thu 22 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Wed 21 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Tue 20 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Mon 19 Oct | Litoměřice hor.n. 21:14 | No data | — |
| Fri 16 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Thu 15 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Wed 14 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Tue 13 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Mon 12 Oct | Litoměřice hor.n. 21:14 | No data | — |
| Fri 9 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Thu 8 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Wed 7 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Tue 6 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Mon 5 Oct | Litoměřice hor.n. 21:13 | No data | — |
| Fri 2 Oct | — 21:25 | −1 min | — |
| Thu 1 Oct | — 21:26 | 0 min | — |
| Wed 30 Sept | — 21:41 | +15 min | +15 min |
| Tue 29 Sept | — 21:27 | 0 min | — |
| Fri 25 Sept | — 21:27 | 0 min | +1 min |
| Thu 24 Sept | — 21:26 | 0 min | — |