Os 14968 14968 N. Město na M. – Žďár n.S.

View line Os 14968

N. Město na M. 12:00 → Žďár n.S. 12:19 Daily 0 h 19 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 12:00 from N. Město na M. · Thu 5 Nov

Next departure 12:00 today · N. Město na M.
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
98%
58/59 runs under 3 min
RT coverage: 59 full · 0 partial · 30 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 Žďár n.S., 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 15 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 58
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 88% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 59 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
12:00on time on time
12:03≈ on time ≈ on time
12:07≈ on time ≈ on time
12:11 / 12:12≈ on time ≈ on time
12:19on 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
Wed 4 NovŽďár n.S. 12:19No data—
Tue 3 NovŽďár n.S. 12:19No data—
Mon 2 NovŽďár n.S. 12:19No data—
Sun 1 NovŽďár n.S. 12:20No data—
Sat 31 OctŽďár n.S. 12:20No data—
Fri 30 OctŽďár n.S. 12:20No data—
Thu 29 OctŽďár n.S. 12:20No data—
Wed 28 OctŽďár n.S. 12:20No data—
Tue 27 OctŽďár n.S. 12:20No data—
Mon 26 OctŽďár n.S. 12:20No data—
Sun 25 OctŽďár n.S. 12:20No data—
Sat 24 OctŽďár n.S. 12:20No data—
Fri 23 OctŽďár n.S. 12:20No data—
Thu 22 OctŽďár n.S. 12:20No data—
Wed 21 OctŽďár n.S. 12:20No data—
Tue 20 OctŽďár n.S. 12:20No data—
Mon 19 OctŽďár n.S. 12:20No data—
Sun 18 OctŽďár n.S. 12:20No data—
Sat 17 OctŽďár n.S. 12:20No data—
Fri 16 OctŽďár n.S. 12:20No data—
Thu 15 OctŽďár n.S. 12:20No data—
Wed 14 OctŽďár n.S. 12:20No data—
Tue 13 OctŽďár n.S. 12:20No data—
Mon 12 OctŽďár n.S. 12:20No data—
Sun 11 OctŽďár n.S. 12:20No data—
Sat 10 OctŽďár n.S. 12:20No data—
Fri 9 OctŽďár n.S. 12:20No data—
Thu 8 OctŽďár n.S. 12:20No data—
Wed 7 OctŽďár n.S. 12:20No data—
Tue 6 OctŽďár n.S. 12:20No data—