Os 25714 25714 Kunčice nad Labem – Vrchlabí
Alerts for train 25714
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 25714.
✓ Today’s run finished
Today, last fix heading to Vrchlabí at 11:23 No data
- Kunčice nad Labem11:14
- Podhůří11:17
- Vrchlabí11:21
Next service: tomorrow 11:14 from Kunčice nad Labem · Wed 11 Nov
Last 30 days
Arrival delay at Vrchlabí, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 24 Sept Max en route +9 min · last fix heading to — +8 min
- Wed 23 Sept Max en route +5 min · last fix heading to — +5 min
- Tue 18 Aug Max en route +5 min · last fix heading to — +5 min
- Mon 5 Oct Max en route +5 min · last fix heading to — +4 min
- Thu 1 Oct Max en route +5 min · last fix heading to — +4 min
Distribution · 90 days
54 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 49
- 3–10 min 9% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 86% T n=7
- 86% W n=7
- 75% T n=8
- 100% F n=8
- 100% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 54 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 |
|---|---|---|---|
| 11:14 | on time | +3 min | |
| 11:17 | ≈ on time | ≈ +2 min | |
| 11:21 | on time | +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 |
|---|---|---|---|
| Tue 10 Nov | Vrchlabí 11:23 | No data | — |
| Mon 9 Nov | Vrchlabí 11:22 | No data | — |
| Sun 8 Nov | Vrchlabí 11:22 | No data | — |
| Sat 7 Nov | Vrchlabí 11:22 | No data | — |
| Fri 6 Nov | Vrchlabí 11:22 | No data | — |
| Thu 5 Nov | Vrchlabí 11:22 | No data | — |
| Wed 4 Nov | Vrchlabí 11:22 | No data | — |
| Tue 3 Nov | Vrchlabí 11:22 | No data | — |
| Mon 2 Nov | Vrchlabí 11:22 | No data | — |
| Sun 1 Nov | Vrchlabí 11:22 | No data | — |
| Sat 31 Oct | Vrchlabí 11:22 | No data | — |
| Fri 30 Oct | Vrchlabí 11:22 | No data | — |
| Thu 29 Oct | Vrchlabí 11:22 | No data | — |
| Wed 28 Oct | Vrchlabí 11:22 | No data | — |
| Tue 27 Oct | Vrchlabí 11:22 | No data | — |
| Mon 26 Oct | Vrchlabí 11:22 | No data | — |
| Sun 25 Oct | Vrchlabí 11:22 | No data | — |
| Sat 24 Oct | Vrchlabí 11:22 | No data | — |
| Fri 23 Oct | Vrchlabí 11:22 | No data | — |
| Thu 22 Oct | Vrchlabí 11:22 | No data | — |
| Wed 21 Oct | Vrchlabí 11:22 | No data | — |
| Tue 20 Oct | Vrchlabí 11:22 | No data | — |
| Mon 19 Oct | Vrchlabí 11:22 | No data | — |
| Sun 18 Oct | Vrchlabí 11:22 | No data | — |
| Sat 17 Oct | Vrchlabí 11:22 | No data | — |
| Fri 16 Oct | Vrchlabí 11:22 | No data | — |
| Thu 15 Oct | Vrchlabí 11:22 | No data | — |
| Wed 14 Oct | Vrchlabí 11:22 | No data | — |
| Tue 13 Oct | Vrchlabí 11:22 | No data | — |
| Mon 12 Oct | Vrchlabí 11:22 | No data | — |