Os 24967 24967 Velké Meziříčí – Studenec

View line Os 24967

Velké Meziříčí 16:49 → Studenec 17:28 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 10 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 16:49 from Velké Meziříčí · Mon 9 Nov

Next departure 16:49 tomorrow · Velké Meziříčí
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
95%
36/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Studenec, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 11 Aug Max en route +9 min · last fix heading to — +9 min
  • Thu 24 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 36
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 88% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 stops).

Last 90 days, 38 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
16:49on time on time
16:51 / 16:52≈ on time ≈ on time
16:56≈ on time ≈ on time
17:00≈ on time ≈ on time
17:03≈ on time ≈ on time
17:06 / 17:08≈ on time ≈ on time
17:16 / 17:17≈ on time ≈ on time
17:21≈ on time ≈ on time
17:24≈ on time ≈ on time
17:28on time on time

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
Fri 6 NovStudenec 17:29No data—
Thu 5 NovStudenec 17:29No data—
Wed 4 NovStudenec 17:29No data—
Tue 3 NovStudenec 17:29No data—
Mon 2 NovStudenec 17:29No data—
Fri 30 OctStudenec 17:29No data—
Thu 29 OctStudenec 17:29No data—
Tue 27 OctStudenec 17:29No data—
Mon 26 OctStudenec 17:29No data—
Fri 23 OctStudenec 17:30No data—
Thu 22 OctStudenec 17:29No data—
Wed 21 OctStudenec 17:29No data—
Tue 20 OctStudenec 17:30No data—
Mon 19 OctStudenec 17:29No data—
Fri 16 OctStudenec 17:29No data—
Thu 15 OctStudenec 17:29No data—
Wed 14 OctStudenec 17:29No data—
Tue 13 OctStudenec 17:29No data—
Mon 12 OctStudenec 17:30No data—
Fri 9 OctStudenec 17:29No data—
Thu 8 OctStudenec 17:29No data—
Wed 7 OctStudenec 17:29No data—
Tue 6 OctStudenec 17:29No data—
Mon 5 OctStudenec 17:27No data—
Fri 2 Oct— 17:41−1 min—
Thu 1 Oct— 17:420 min—
Wed 30 Sept— 17:430 min—
Tue 29 Sept— 17:420 min—
Fri 25 Sept— 17:430 min—
Thu 24 Sept— 17:45+3 min+3 min