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

View line Os 24907

Žďár n.S. 06:30 → Studenec 07:55 Tue, Sat, Sun 1 h 25 min · 16 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Tuesday 17 November No data

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

Next departure 06:30 today · Žďár n.S.
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 14 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

Worst days

  • Sat 29 Aug Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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