Os 14801 14801 Okříšky – Třebíč

View line Os 14801

Okříšky 04:50 → Třebíč 05:04 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Třebíč at 05:04 No data

  1. Okříšky04:50
  2. Krahulov04:57
  3. Třebíč - Borovina05:00
  4. Třebíč05:04

Next service: Monday 04:50 from Okříšky · Mon 9 Nov

Next departure 04:50 Monday · Okříšky
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 23 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 Třebíč, in minutes. One bar per run.

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

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 100% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% 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 (4 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
04:50on time on time
04:57≈ on time ≈ +1 min
05:00≈ on time ≈ +1 min
05:04on 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
Fri 6 NovTřebíč 05:04No data—
Thu 5 NovTřebíč 05:04No data—
Wed 4 NovTřebíč 05:04No data—
Tue 3 NovTřebíč 05:05No data—
Mon 2 NovTřebíč 05:04No data—
Fri 30 OctTřebíč 05:05No data—
Thu 29 OctTřebíč 05:05No data—
Tue 27 OctTřebíč 05:05No data—
Mon 26 OctTřebíč 05:05No data—
Fri 23 OctTřebíč 05:05No data—
Thu 22 OctTřebíč 05:05No data—
Wed 21 OctTřebíč 05:05No data—
Tue 20 OctTřebíč 05:05No data—
Mon 19 OctTřebíč 05:05No data—
Fri 16 OctTřebíč 05:05No data—
Thu 15 OctTřebíč 05:05No data—
Wed 14 OctTřebíč 05:05No data—
Tue 13 OctTřebíč 05:05No data—
Mon 12 OctTřebíč 05:05No data—
Fri 9 OctTřebíč 05:05No data—
Thu 8 OctTřebíč 05:05No data—
Wed 7 OctTřebíč 05:05No data—
Tue 6 OctTřebíč 05:05No data—
Tue 29 Sept— 05:180 min—
Fri 25 Sept— 05:200 min—
Thu 24 Sept— 05:19+1 min+1 min
Wed 23 Sept— 05:19+1 min+1 min
Tue 22 Sept— 05:190 min—
Mon 21 Sept— 05:19+1 min+1 min
Fri 18 Sept— 05:19+1 min+1 min