Os 14800 14800 Třebíč – Jihlava

View line Os 14800

Třebíč 05:11 → Jihlava 06:05 Mon, Tue, Wed, Thu, Fri 0 h 54 min · 12 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 05:11 from Třebíč · Fri 6 Nov

Next departure 05:11 today · Třebíč
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
92%
33/36 runs under 3 min
RT coverage: 36 full · 0 partial · 22 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Jihlava, 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 +6 min · last fix heading to — +4 min
  • Tue 8 Sept Max en route +6 min · last fix heading to — +4 min
  • Tue 1 Sept Max en route +6 min · last fix heading to — +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 63% T n=8
  • 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 (12 stops).

Last 90 days, 36 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:11on time on time
05:14≈ on time ≈ on time
05:19 / 05:22≈ on time ≈ +1 min
05:29≈ on time ≈ +1 min
05:35≈ on time ≈ +1 min
05:39≈ 1 min early ≈ +1 min
05:42≈ 1 min early ≈ +1 min
05:45 / 05:46≈ 1 min early ≈ +1 min
05:49≈ 1 min early ≈ +1 min
05:52≈ 1 min early ≈ +1 min
06:00≈ 1 min early ≈ +1 min
06:051 min early +2 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
Thu 5 NovJihlava 06:04No data—
Wed 4 NovJihlava 06:04No data—
Tue 3 NovJihlava 06:05No data—
Mon 2 NovJihlava 06:04No data—
Fri 30 OctJihlava 06:06No data—
Thu 29 OctJihlava 06:06No data—
Tue 27 OctJihlava 06:06No data—
Mon 26 OctJihlava 06:06No data—
Fri 23 OctJihlava 06:06No data—
Thu 22 OctJihlava 06:06No data—
Wed 21 OctJihlava 06:06No data—
Tue 20 OctJihlava 06:06No data—
Mon 19 OctJihlava 06:06No data—
Fri 16 OctJihlava 06:06No data—
Thu 15 OctJihlava 06:06No data—
Wed 14 OctJihlava 06:06No data—
Tue 13 OctJihlava 06:06No data—
Mon 12 OctJihlava 06:06No data—
Fri 9 OctJihlava 06:06No data—
Thu 8 OctJihlava 06:06No data—
Wed 7 OctJihlava 06:06No data—
Tue 6 OctJihlava 06:07No data—
Tue 29 Sept— 06:190 min+2 min
Fri 25 Sept— 06:190 min—
Thu 24 Sept— 06:20+1 min+3 min
Wed 23 Sept— 06:20+1 min+2 min
Tue 22 Sept— 06:190 min+1 min
Mon 21 Sept— 06:190 min+2 min
Fri 18 Sept— 06:190 min+2 min
Thu 17 Sept— 06:19−1 min—