Os 25718 25718 Kunčice nad Labem – Vrchlabí

View line Os 25718

Kunčice nad Labem 13:14 → Vrchlabí 13:21 Daily 0 h 07 min · 3 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 11 November No data

Next service: today 13:14 from Kunčice nad Labem · Thu 12 Nov

Next departure 13:14 today · Kunčice nad Labem
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
87%
45/52 runs under 3 min
RT coverage: 52 full · 0 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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 +6 min · last fix heading to — +6 min
  • Mon 28 Sept Max en route +5 min · last fix heading to — +4 min
  • Wed 23 Sept Max en route +4 min · last fix heading to — +4 min
  • Tue 25 Aug Max en route +5 min · last fix heading to — +4 min
  • Thu 1 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

52 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 87% · 45
  • 3–10 min 13% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 57% T n=7
  • 86% W n=7
  • 71% T n=7
  • 100% F n=7
  • 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, 52 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.

StopSched.Usually 9 days in 10
13:14on time +4 min
13:17≈ on time ≈ +4 min
13:21on time +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

DateLast stopFinalMax
Wed 11 NovVrchlabí 13:22No data—
Tue 10 NovVrchlabí 13:22No data—
Mon 9 NovVrchlabí 13:22No data—
Sun 8 NovVrchlabí 13:22No data—
Sat 7 NovVrchlabí 13:22No data—
Fri 6 NovVrchlabí 13:22No data—
Thu 5 NovVrchlabí 13:22No data—
Wed 4 NovVrchlabí 13:22No data—
Tue 3 NovVrchlabí 13:22No data—
Mon 2 NovVrchlabí 13:22No data—
Sun 1 NovVrchlabí 13:22No data—
Sat 31 OctVrchlabí 13:22No data—
Fri 30 OctVrchlabí 13:22No data—
Thu 29 OctVrchlabí 13:22No data—
Wed 28 OctVrchlabí 13:22No data—
Tue 27 OctVrchlabí 13:22No data—
Mon 26 OctVrchlabí 13:22No data—
Sun 25 OctVrchlabí 13:22No data—
Sat 24 OctVrchlabí 13:22No data—
Fri 23 OctVrchlabí 13:22No data—
Thu 22 OctVrchlabí 13:22No data—
Wed 21 OctVrchlabí 13:22No data—
Tue 20 OctVrchlabí 13:22No data—
Mon 19 OctVrchlabí 13:22No data—
Sun 18 OctVrchlabí 13:22No data—
Sat 17 OctVrchlabí 13:22No data—
Fri 16 OctVrchlabí 13:22No data—
Thu 15 OctVrchlabí 13:22No data—
Wed 14 OctVrchlabí 13:22No data—
Tue 13 OctVrchlabí 13:22No data—