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

View line Os 24961

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

✓ Today’s run finished

Today, last fix heading to Studenec at 06:18 No data

  1. Velké Meziříčí05:38
  2. Oslavice05:45
  3. Oslavička05:49
  4. Rudíkov05:54
  5. Budišov u Třebíče06:04
  6. Pozďatín06:12
  7. Studenec06:16

Next service: Wednesday 05:38 from Velké Meziříčí · Wed 18 Nov

Next departure 05:38 Wednesday · Velké Meziříčí
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
05:38on time on time
05:40 / 05:41≈ on time ≈ on time
05:45≈ on time ≈ on time
05:49≈ on time ≈ on time
05:52≈ on time ≈ on time
05:54 / 05:56≈ on time ≈ on time
06:04 / 06:05≈ on time ≈ +1 min
06:09≈ on time ≈ +1 min
06:12≈ on time ≈ +1 min
06:16on time +1 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
Mon 16 NovStudenec 06:18No data—
Fri 13 NovStudenec 06:17No data—
Thu 12 NovStudenec 06:17No data—
Wed 11 NovStudenec 06:17No data—
Tue 10 NovStudenec 06:17No data—
Mon 9 NovStudenec 06:17No data—
Fri 6 NovStudenec 06:17No data—
Thu 5 NovStudenec 06:17No data—
Wed 4 NovStudenec 06:17No data—
Tue 3 NovStudenec 06:18No data—
Mon 2 NovStudenec 06:17No data—
Fri 30 OctStudenec 06:17No data—
Thu 29 OctStudenec 06:17No data—
Tue 27 OctStudenec 06:17No data—
Mon 26 OctStudenec 06:17No data—
Fri 23 OctStudenec 06:17No data—
Thu 22 OctStudenec 06:17No data—
Wed 21 OctStudenec 06:17No data—
Tue 20 OctStudenec 06:17No data—
Mon 19 OctStudenec 06:17No data—
Fri 16 OctStudenec 06:17No data—
Thu 15 OctStudenec 06:17No data—
Wed 14 OctStudenec 06:17No data—
Tue 13 OctStudenec 06:17No data—
Mon 12 OctStudenec 06:17No data—
Fri 9 OctStudenec 06:17No data—
Thu 8 OctStudenec 06:17No data—
Wed 7 OctStudenec 06:17No data—
Tue 6 OctStudenec 06:18No data—
Mon 5 Oct— 06:300 min—