Os 25521 25521 Most – Lovosice
Alerts for train 25521
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 25521.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 22:27 from Most · 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
- Sat 22 Aug Max en route +13 min · last fix heading to — +10 min
- Fri 25 Sept Max en route +12 min · last fix heading to — +8 min
- Mon 10 Aug Max en route +8 min · last fix heading to — +3 min
Distribution · 90 days
58 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 38% · 22
- On time 57% · 33
- 3–10 min 3% · 2
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=8
- 100% W n=8
- 100% T n=8
- 88% F n=8
- 89% S n=9
- 100% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 58 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 |
|---|---|---|---|
| 22:27 | on time | on time | |
| 22:31 | ≈ on time | ≈ on time | |
| 22:40 | ≈ on time | ≈ +1 min | |
| 22:46 | ≈ on time | ≈ +1 min | |
| 22:49 | ≈ on time | ≈ +1 min | |
| 22:56 / 23:00 | ≈ on time | ≈ +1 min | |
| 23:04 | ≈ 1 min early | ≈ +1 min | |
| 23:06 | ≈ 1 min early | ≈ +1 min | |
| 23:09 | ≈ 1 min early | ≈ +1 min | |
| 23:11 / 23:12 | ≈ 1 min early | ≈ +1 min | |
| 23:16 / 23:18 | ≈ 1 min early | ≈ +2 min | |
| 23:22 | ≈ 1 min early | ≈ +2 min | |
| 23:27 | 1 min early | +2 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 |
|---|---|---|---|
| Wed 4 Nov | Lovosice 23:28 | No data | — |
| Tue 3 Nov | Lovosice 23:28 | No data | — |
| Mon 2 Nov | Lovosice 23:28 | No data | — |
| Sun 1 Nov | Lovosice 23:28 | No data | — |
| Sat 31 Oct | Lovosice 23:28 | No data | — |
| Fri 30 Oct | Lovosice 23:28 | No data | — |
| Thu 29 Oct | Lovosice 23:28 | No data | — |
| Wed 28 Oct | Lovosice 23:28 | No data | — |
| Tue 27 Oct | Lovosice 23:29 | No data | — |
| Mon 26 Oct | Lovosice 23:28 | No data | — |
| Sun 25 Oct | Lovosice 23:28 | No data | — |
| Sat 24 Oct | Lovosice 23:28 | No data | — |
| Fri 23 Oct | Lovosice 23:28 | No data | — |
| Thu 22 Oct | Lovosice 23:28 | No data | — |
| Wed 21 Oct | Lovosice 23:28 | No data | — |
| Tue 20 Oct | Lovosice 23:28 | No data | — |
| Mon 19 Oct | Lovosice 23:29 | No data | — |
| Sun 18 Oct | Lovosice 23:28 | No data | — |
| Sat 17 Oct | Lovosice 23:28 | No data | — |
| Fri 16 Oct | Lovosice 23:28 | No data | — |
| Thu 15 Oct | Lovosice 23:28 | No data | — |
| Wed 14 Oct | Lovosice 23:28 | No data | — |
| Tue 13 Oct | Lovosice 23:28 | No data | — |
| Mon 12 Oct | Lovosice 23:28 | No data | — |
| Sun 11 Oct | Lovosice 23:28 | No data | — |
| Sat 10 Oct | Lovosice 23:28 | No data | — |
| Fri 9 Oct | Lovosice 23:28 | No data | — |
| Thu 8 Oct | Lovosice 23:28 | No data | — |
| Wed 7 Oct | Lovosice 23:28 | No data | — |
| Tue 6 Oct | Lovosice 23:28 | No data | — |