Os 14839 14839 Jihlava – Okříšky

View line Os 14839

Jihlava 17:53 → Okříšky 18:28 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 9 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:53 from Jihlava · Fri 6 Nov

Next departure 17:53 today · Jihlava
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
71%
27/38 runs under 3 min
RT coverage: 38 full · 0 partial · 23 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Okříšky, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 17 Aug Max en route +35 min · last fix heading to — +35 min
  • Thu 20 Aug Max en route +29 min · last fix heading to — +27 min
  • Fri 21 Aug Max en route +27 min · last fix heading to — +25 min
  • Tue 22 Sept Max en route +13 min · last fix heading to — +8 min
  • Mon 7 Sept Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 24% · 9
  • On time 47% · 18
  • 3–10 min 21% · 8
  • 10–30 min 5% · 2
  • 30+ min 3% · 1

On-time by weekday

  • 71% M n=7
  • 75% T n=8
  • 88% W n=8
  • 71% T n=7
  • 50% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 38 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
17:53on time +7 min
17:56 / 17:57≈ on time ≈ +8 min
18:04 / 18:05≈ on time ≈ +9 min
18:07 / 18:08≈ on time ≈ +9 min
18:10 / 18:11≈ on time ≈ +9 min
18:14≈ on time ≈ +9 min
18:17≈ on time ≈ +8 min
18:21≈ 1 min early ≈ +8 min
18:281 min early +8 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 NovOkříšky 18:29No data—
Wed 4 NovOkříšky 18:29No data—
Tue 3 NovOkříšky 18:29No data—
Mon 2 NovOkříšky 18:29No data—
Fri 30 OctOkříšky 18:29No data—
Thu 29 OctOkříšky 18:29No data—
Tue 27 OctOkříšky 18:30No data—
Mon 26 OctOkříšky 18:29No data—
Fri 23 OctOkříšky 18:30No data—
Thu 22 OctOkříšky 18:29No data—
Wed 21 OctOkříšky 18:29No data—
Tue 20 OctOkříšky 18:30No data—
Mon 19 OctOkříšky 18:29No data—
Fri 16 OctOkříšky 18:29No data—
Thu 15 OctOkříšky 18:29No data—
Wed 14 OctOkříšky 18:29No data—
Tue 13 OctOkříšky 18:29No data—
Mon 12 OctOkříšky 18:30No data—
Fri 9 OctOkříšky 18:29No data—
Thu 8 OctOkříšky 18:29No data—
Wed 7 OctOkříšky 18:29No data—
Tue 6 OctOkříšky 18:29No data—
Mon 5 OctOkříšky 18:29No data—
Fri 2 Oct— 19:13+4 min+4 min
Thu 1 Oct— 19:14+4 min+4 min
Wed 30 Sept— 19:14+4 min+4 min
Tue 29 Sept— 19:14+5 min+5 min
Fri 25 Sept— 18:46+3 min+5 min
Thu 24 Sept— 18:40−2 min—
Wed 23 Sept— 18:42−1 min—