Os 14808 14808 Třebíč – Jihlava

View line Os 14808

Třebíč 09:15 → Jihlava 10:08 Sat, Sun 0 h 53 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 8 November No data

Next service: Saturday 09:15 from Třebíč · Sat 14 Nov

Next departure 09:15 Saturday · Třebíč
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
76%
13/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+3min
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

  • Sat 5 Sept Max en route +13 min · last fix heading to — +8 min
  • Mon 28 Sept Max en route +5 min · last fix heading to — +3 min
  • Sat 19 Sept Max en route +3 min · last fix heading to — +3 min
  • Sun 23 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 71% · 12
  • 3–10 min 24% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 75% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 17 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
09:15on time +4 min
09:18≈ on time ≈ +4 min
09:23≈ on time ≈ +4 min
09:30≈ +1 min ≈ +4 min
09:35 / 09:36≈ +1 min ≈ +4 min
09:40≈ +1 min ≈ +4 min
09:43≈ +1 min ≈ +3 min
09:46 / 09:47≈ +1 min ≈ +3 min
09:50≈ +1 min ≈ +3 min
09:53 / 09:56≈ +1 min ≈ +3 min
10:03 / 10:04≈ +1 min ≈ +3 min
10:08+1 min +3 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
Sun 8 NovJihlava 10:09No data—
Sat 7 NovJihlava 10:09No data—
Sun 1 NovJihlava 10:09No data—
Sat 31 OctJihlava 10:09No data—
Wed 28 OctJihlava 10:09No data—
Sun 25 OctJihlava 10:09No data—
Sat 24 OctJihlava 10:09No data—
Sun 18 OctJihlava 10:09No data—
Sat 17 OctJihlava 10:09No data—
Sun 11 OctJihlava 10:09No data—
Sat 10 OctJihlava 10:09No data—
Sun 4 Oct— 10:170 min—
Sat 3 Oct— 10:160 min—
Mon 28 Sept— 10:25+3 min+5 min
Sun 27 Sept— 10:240 min+1 min
Sat 26 Sept— 10:25+2 min+2 min
Sun 20 Sept— 10:24+2 min+2 min
Sat 19 Sept— 10:26+3 min+3 min
Sun 13 Sept— 10:24+2 min+2 min
Sat 12 Sept— 10:24+1 min+2 min
Sun 6 Sept— 10:20−2 min—
Sat 5 Sept— 10:31+8 min+13 min
Sun 30 Aug— 10:21−1 min+2 min
Sat 29 Aug— 10:22−1 min+3 min
Sun 23 Aug— 10:25+3 min+3 min
Sat 22 Aug— 10:24+2 min+5 min
Sun 16 Aug— 10:220 min+2 min
Sat 15 Aug— 10:230 min—