Os 25700 25700 Kunčice nad Labem – Vrchlabí
Alerts for train 25700
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 25700.
✓ Today’s run finished
Today, last fix heading to Vrchlabí at 04:59 No data
- Kunčice nad Labem04:53
- Podhůří04:56
- Vrchlabí05:00
Next service: tomorrow 04:53 from Kunčice nad Labem · Thu 12 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 20 Aug Max en route +26 min · last fix heading to — +26 min
- Sat 5 Sept Max en route +10 min · last fix heading to — +10 min
- Sat 22 Aug Max en route +10 min · last fix heading to — +9 min
- Sat 19 Sept Max en route +4 min · last fix heading to — +4 min
- Sat 29 Aug Max en route +4 min · last fix heading to — +3 min
Distribution · 90 days
53 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 48
- 3–10 min 6% · 3
- 10–30 min 4% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 100% T n=7
- 100% W n=7
- 86% T n=7
- 100% F n=8
- 50% 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, 53 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 |
|---|---|---|---|
| 04:53 | on time | +2 min | |
| 04:56 | ≈ on time | ≈ +2 min | |
| 05:00 | 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 |
|---|---|---|---|
| Wed 11 Nov | Vrchlabí 04:59 | No data | — |
| Tue 10 Nov | Vrchlabí 04:59 | No data | — |
| Mon 9 Nov | Vrchlabí 04:59 | No data | — |
| Sun 8 Nov | Vrchlabí 04:59 | No data | — |
| Sat 7 Nov | Vrchlabí 04:59 | No data | — |
| Fri 6 Nov | Vrchlabí 04:59 | No data | — |
| Thu 5 Nov | Vrchlabí 04:59 | No data | — |
| Wed 4 Nov | Vrchlabí 04:59 | No data | — |
| Tue 3 Nov | Vrchlabí 04:59 | No data | — |
| Mon 2 Nov | Vrchlabí 04:59 | No data | — |
| Sun 1 Nov | Vrchlabí 05:01 | No data | — |
| Sat 31 Oct | Vrchlabí 05:01 | No data | — |
| Fri 30 Oct | Vrchlabí 05:01 | No data | — |
| Thu 29 Oct | Vrchlabí 05:01 | No data | — |
| Wed 28 Oct | Vrchlabí 05:02 | No data | — |
| Tue 27 Oct | Vrchlabí 05:01 | No data | — |
| Mon 26 Oct | Vrchlabí 05:01 | No data | — |
| Sun 25 Oct | Vrchlabí 05:01 | No data | — |
| Sat 24 Oct | Vrchlabí 05:01 | No data | — |
| Fri 23 Oct | Vrchlabí 05:01 | No data | — |
| Thu 22 Oct | Vrchlabí 05:01 | No data | — |
| Wed 21 Oct | Vrchlabí 05:01 | No data | — |
| Tue 20 Oct | Vrchlabí 05:01 | No data | — |
| Mon 19 Oct | Vrchlabí 05:01 | No data | — |
| Sun 18 Oct | Vrchlabí 05:01 | No data | — |
| Sat 17 Oct | Vrchlabí 05:01 | No data | — |
| Fri 16 Oct | Vrchlabí 05:01 | No data | — |
| Thu 15 Oct | Vrchlabí 05:01 | No data | — |
| Wed 14 Oct | Vrchlabí 05:01 | No data | — |
| Tue 13 Oct | Vrchlabí 05:01 | No data | — |