Os 4650 4650 Hustopeče u Brna – Tišnov

View line Os 4650

Hustopeče u Brna 15:41 → Tišnov 16:59 Mon, Tue, Wed, Thu, Fri 1 h 18 min · 22 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:41 from Hustopeče u Brna · Fri 6 Nov

Next departure 15:41 today · Hustopeče u Brna
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
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Tišnov, 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 21 Sept Max en route +8 min · last fix heading to — +7 min
  • Mon 17 Aug Max en route +11 min · last fix heading to — +5 min
  • Thu 13 Aug Max en route +8 min · last fix heading to — +5 min
  • Fri 25 Sept Max en route +5 min · last fix heading to — +3 min
  • Fri 11 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 33
  • 3–10 min 18% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=8
  • 100% W n=8
  • 75% T n=8
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
15:41on time on time
15:47 / 15:48≈ on time ≈ on time
15:50≈ on time ≈ on time
15:51≈ on time ≈ on time
15:54 / 15:58≈ on time ≈ +1 min
16:02≈ on time ≈ +1 min
16:05≈ on time ≈ +1 min
16:07≈ on time ≈ +1 min
16:09 / 16:10≈ on time ≈ +1 min
16:11≈ on time ≈ +1 min
16:13 / 16:14≈ on time ≈ +1 min
16:17≈ on time ≈ +1 min
16:21 / 16:23≈ on time ≈ +2 min
16:26 / 16:27≈ on time ≈ +2 min
16:32 / 16:33≈ on time ≈ +2 min
16:36 / 16:37≈ on time ≈ +2 min
16:39 / 16:40≈ on time ≈ +2 min
16:43 / 16:44≈ on time ≈ +2 min
16:47 / 16:48≈ on time ≈ +3 min
16:53≈ on time ≈ +3 min
16:56≈ on time ≈ +3 min
16:59on time +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
Thu 5 NovTišnov 16:59No data—
Wed 4 NovTišnov 16:59No data—
Tue 3 NovTišnov 16:59No data—
Mon 2 NovTišnov 16:59No data—
Fri 30 OctTišnov 17:00No data—
Thu 29 OctTišnov 17:00No data—
Tue 27 OctTišnov 17:00No data—
Mon 26 OctTišnov 17:00No data—
Fri 23 OctTišnov 17:00No data—
Thu 22 OctTišnov 17:00No data—
Wed 21 OctTišnov 17:00No data—
Tue 20 OctTišnov 17:00No data—
Mon 19 OctTišnov 17:00No data—
Fri 16 OctTišnov 17:00No data—
Thu 15 OctTišnov 17:00No data—
Wed 14 OctTišnov 17:00No data—
Tue 13 OctTišnov 17:00No data—
Mon 12 OctTišnov 17:00No data—
Fri 9 OctTišnov 17:00No data—
Thu 8 OctTišnov 17:00No data—
Wed 7 OctTišnov 17:00No data—
Tue 6 OctTišnov 17:00No data—
Mon 5 OctTišnov 17:000 min—
Fri 2 Oct— 17:130 min—
Thu 1 Oct— 17:130 min+3 min
Wed 30 Sept— 17:140 min+3 min
Tue 29 Sept— 17:12−1 min—
Fri 25 Sept— 17:17+3 min+5 min
Thu 24 Sept— 17:140 min+3 min
Wed 23 Sept— 17:140 min+4 min