Os 24909 24909 Žďár n.S. – Studenec

View line Os 24909

Žďár n.S. 08:30 → Studenec 09:55 Daily 1 h 25 min · 16 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Studenec at 09:54 No data

  1. Žďár n.S.08:30
  2. Sklené nad Oslavou08:43
  3. Martinice u Velkého Meziříčí09:11
  4. Oslavice09:25
  5. Vlčatín09:32
  6. Kojatín09:48
  7. Studenec09:55

Next service: tomorrow 08:30 from Žďár n.S. · Sat 21 Nov

Next departure 08:30 tomorrow · Žďár n.S.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 full · 0 partial · 46 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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
08:30on time on time
08:36≈ on time ≈ on time
08:39≈ on time ≈ on time
08:43 / 08:44≈ on time ≈ on time
08:50 / 09:07≈ on time ≈ on time
09:11≈ on time ≈ on time
09:17 / 09:18≈ on time ≈ on time
09:20 / 09:21≈ on time ≈ on time
09:25≈ on time ≈ on time
09:29≈ on time ≈ on time
09:32≈ on time ≈ on time
09:34 / 09:35≈ on time ≈ on time
09:43 / 09:44≈ on time ≈ on time
09:48≈ on time ≈ on time
09:51≈ on time ≈ on time
09:55on 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 20 NovStudenec 09:54No data—
Thu 19 NovStudenec 09:54No data—
Wed 18 NovStudenec 09:54No data—
Tue 17 NovStudenec 09:54No data—
Mon 16 NovStudenec 09:54No data—
Sun 15 NovStudenec 09:54No data—
Sat 14 NovStudenec 09:54No data—
Fri 13 NovStudenec 09:54No data—
Thu 12 NovStudenec 09:54No data—
Wed 11 NovStudenec 09:54No data—
Tue 10 NovStudenec 09:54No data—
Mon 9 NovStudenec 09:54No data—
Sun 8 NovStudenec 09:54No data—
Sat 7 NovStudenec 09:54No data—
Fri 6 NovStudenec 09:54No data—
Thu 5 NovStudenec 09:54No data—
Wed 4 NovStudenec 09:54No data—
Tue 3 NovStudenec 09:54No data—
Mon 2 NovStudenec 09:54No data—
Sun 1 NovStudenec 09:56No data—
Sat 31 OctStudenec 09:56No data—
Fri 30 OctStudenec 09:56No data—
Thu 29 OctStudenec 09:56No data—
Wed 28 OctStudenec 09:56No data—
Tue 27 OctStudenec 09:57No data—
Mon 26 OctStudenec 09:56No data—
Sun 25 OctStudenec 09:56No data—
Sat 24 OctStudenec 09:56No data—
Fri 23 OctStudenec 09:57No data—
Thu 22 OctStudenec 09:57No data—