Os 25514 25514 Litoměřice hor.n. – Most
Alerts for train 25514
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 25514.
It has not run yet today
Last recorded run: Sunday 8 November No data
Next service: today 16:14 from Litoměřice hor.n. · Mon 9 Nov
Last 30 days
Arrival delay at Most, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 29 Aug Max en route +13 min · last fix heading to — +12 min
- Fri 11 Sept Max en route +7 min · last fix heading to — +6 min
- Sat 5 Sept Max en route +8 min · last fix heading to — +5 min
- Tue 22 Sept Max en route +8 min · last fix heading to — +4 min
- Sat 12 Sept Max en route +6 min · last fix heading to — +3 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 27% · 15
- On time 62% · 34
- 3–10 min 9% · 5
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 86% T n=7
- 100% W n=8
- 100% T n=8
- 75% F n=8
- 63% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 55 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 |
|---|---|---|---|
| 16:14 | +2 min | +7 min | |
| 16:16 | ≈ +2 min | ≈ +7 min | |
| 16:19 | ≈ +2 min | ≈ +7 min | |
| 16:22 | ≈ +2 min | ≈ +6 min | |
| 16:25 / 16:32 | ≈ +2 min | ≈ +6 min | |
| 16:36 | ≈ +2 min | ≈ +5 min | |
| 16:38 / 16:39 | ≈ +1 min | ≈ +5 min | |
| 16:43 | ≈ +1 min | ≈ +4 min | |
| 16:45 | ≈ +1 min | ≈ +4 min | |
| 16:49 | ≈ +1 min | ≈ +4 min | |
| 16:50 | ≈ +1 min | ≈ +4 min | |
| 16:56 / 16:57 | ≈ +1 min | ≈ +3 min | |
| 17:03 | ≈ on time | ≈ +3 min | |
| 17:06 | ≈ on time | ≈ +3 min | |
| 17:12 | ≈ on time | ≈ +3 min | |
| 17:23 | ≈ 1 min early | ≈ +3 min | |
| 17:27 | 1 min early | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 8 Nov | Most 17:28 | No data | — |
| Sat 7 Nov | Most 17:28 | No data | — |
| Fri 6 Nov | Most 17:28 | No data | — |
| Thu 5 Nov | Most 17:28 | No data | — |
| Wed 4 Nov | Most 17:28 | No data | — |
| Tue 3 Nov | Most 17:28 | No data | — |
| Mon 2 Nov | Most 17:28 | No data | — |
| Sun 1 Nov | Most 17:28 | No data | — |
| Sat 31 Oct | Most 17:28 | No data | — |
| Fri 30 Oct | Most 17:28 | No data | — |
| Thu 29 Oct | Most 17:28 | No data | — |
| Wed 28 Oct | Most 17:28 | No data | — |
| Tue 27 Oct | Most 17:28 | No data | — |
| Mon 26 Oct | Most 17:28 | No data | — |
| Sun 25 Oct | Most 17:28 | No data | — |
| Sat 24 Oct | Most 17:28 | No data | — |
| Fri 23 Oct | Most 17:29 | No data | — |
| Thu 22 Oct | Most 17:28 | No data | — |
| Wed 21 Oct | Most 17:28 | No data | — |
| Tue 20 Oct | Most 17:29 | No data | — |
| Mon 19 Oct | Most 17:28 | No data | — |
| Sun 18 Oct | Most 17:28 | No data | — |
| Sat 17 Oct | Most 17:28 | No data | — |
| Fri 16 Oct | Most 17:28 | No data | — |
| Thu 15 Oct | Most 17:28 | No data | — |
| Wed 14 Oct | Most 17:28 | No data | — |
| Tue 13 Oct | Most 17:28 | No data | — |
| Mon 12 Oct | Most 17:29 | No data | — |
| Sun 11 Oct | Most 17:28 | No data | — |
| Sat 10 Oct | Most 17:28 | No data | — |