Os 28313 28313 Dačice – Slavonice

View line Os 28313

Dačice 06:21 → Slavonice 06:50 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 7 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 06:21 from Dačice · Mon 9 Nov

Next departure 06:21 tomorrow · Dačice
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Slavonice, 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

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

  • Early 8% · 3
  • On time 92% · 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=8
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
06:21on time on time
06:22 / 06:23≈ on time ≈ on time
06:30≈ on time ≈ on time
06:34≈ on time ≈ on time
06:38≈ 1 min early ≈ on time
06:42≈ 1 min early ≈ on time
06:501 min early on time

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 NovSlavonice 06:49No data—
Thu 5 NovSlavonice 06:49No data—
Wed 4 NovSlavonice 06:49No data—
Tue 3 NovSlavonice 06:49No data—
Mon 2 NovSlavonice 06:49No data—
Fri 30 OctSlavonice 06:51No data—
Thu 29 OctSlavonice 06:51No data—
Tue 27 OctSlavonice 06:51No data—
Mon 26 OctSlavonice 06:51No data—
Fri 23 OctSlavonice 06:51No data—
Thu 22 OctSlavonice 06:51No data—
Wed 21 OctSlavonice 06:51No data—
Tue 20 OctSlavonice 06:51No data—
Mon 19 OctSlavonice 06:51No data—
Fri 16 OctSlavonice 06:51No data—
Thu 15 OctSlavonice 06:51No data—
Wed 14 OctSlavonice 06:51No data—
Tue 13 OctSlavonice 06:51No data—
Mon 12 OctSlavonice 06:51No data—
Fri 9 OctSlavonice 06:51No data—
Thu 8 OctSlavonice 06:51No data—
Wed 7 OctSlavonice 06:51No data—
Tue 6 OctSlavonice 06:51No data—
Mon 5 Oct— 07:050 min—
Fri 2 Oct— 07:060 min—
Thu 1 Oct— 07:04−1 min—
Wed 30 Sept— 07:040 min—
Tue 29 Sept— 07:040 min—
Fri 25 Sept— 07:040 min+1 min
Thu 24 Sept— 07:040 min—