Os 22806 22806 Náměšť nad Oslavou – Třebíč

View line Os 22806

Náměšť nad Oslavou 05:48 → Třebíč 06:15 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 4 stops České dráhy, a.s.

It does not run today

Last recorded run: Monday 16 November No data

Next service: tomorrow 05:48 from Náměšť nad Oslavou · Wed 18 Nov

Next departure 05:48 tomorrow · Náměšť nad Oslavou
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
94%
29/31 runs under 3 min
RT coverage: 31 full · 0 partial · 29 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

Worst days

  • Wed 30 Sept Max en route +7 min · last fix heading to — +7 min
  • Mon 7 Sept Max en route +10 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 83% W n=6
  • 100% T n=6
  • 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, 31 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:48on time on time
05:54 / 05:55≈ on time ≈ on time
06:03≈ on time ≈ +1 min
06:15on 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
Mon 16 NovTřebíč 06:14No data—
Fri 13 NovTřebíč 06:14No data—
Thu 12 NovTřebíč 06:14No data—
Wed 11 NovTřebíč 06:14No data—
Tue 10 NovTřebíč 06:14No data—
Mon 9 NovTřebíč 06:14No data—
Fri 6 NovTřebíč 06:14No data—
Thu 5 NovTřebíč 06:14No data—
Wed 4 NovTřebíč 06:14No data—
Tue 3 NovTřebíč 06:14No data—
Mon 2 NovTřebíč 06:14No data—
Fri 30 OctTřebíč 06:16No data—
Thu 29 OctTřebíč 06:16No data—
Tue 27 OctTřebíč 06:16No data—
Mon 26 OctTřebíč 06:16No data—
Fri 23 OctTřebíč 06:16No data—
Thu 22 OctTřebíč 06:16No data—
Wed 21 OctTřebíč 06:16No data—
Tue 20 OctTřebíč 06:16No data—
Mon 19 OctTřebíč 06:16No data—
Fri 16 OctTřebíč 06:16No data—
Thu 15 OctTřebíč 06:16No data—
Wed 14 OctTřebíč 06:16No data—
Tue 13 OctTřebíč 06:16No data—
Mon 12 OctTřebíč 06:16No data—
Fri 9 OctTřebíč 06:16No data—
Thu 8 OctTřebíč 06:16No data—
Wed 7 OctTřebíč 06:16No data—
Tue 6 OctTřebíč 06:17No data—
Mon 5 Oct— 06:560 min—