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

View line Os 4642

Hustopeče u Brna 08:41 → Tišnov 09: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 08:41 from Hustopeče u Brna · Fri 6 Nov

Next departure 08: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
88%
35/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

  • Fri 14 Aug Max en route +14 min · last fix heading to — +10 min
  • Wed 16 Sept Max en route +6 min · last fix heading to — +6 min
  • Tue 15 Sept Max en route +5 min · last fix heading to — +5 min
  • Wed 9 Sept Max en route +6 min · last fix heading to — +4 min
  • Mon 14 Sept Max en route +5 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 88% · 35
  • 3–10 min 10% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 88% T n=8
  • 75% W n=8
  • 100% T n=8
  • 88% 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
08:41on time on time
08:47 / 08:48≈ on time ≈ on time
08:50≈ on time ≈ on time
08:51≈ on time ≈ +1 min
08:53 / 08:54≈ on time ≈ +1 min
08:58≈ on time ≈ +1 min
09:01 / 09:02≈ on time ≈ +1 min
09:04≈ on time ≈ +1 min
09:06 / 09:07≈ on time ≈ +1 min
09:08≈ on time ≈ +1 min
09:10 / 09:11≈ on time ≈ +1 min
09:14≈ on time ≈ +1 min
09:18 / 09:23≈ on time ≈ +1 min
09:26 / 09:27≈ on time ≈ +2 min
09:32 / 09:33≈ on time ≈ +2 min
09:36 / 09:37≈ on time ≈ +2 min
09:39 / 09:40≈ on time ≈ +2 min
09:43 / 09:44≈ on time ≈ +2 min
09:47 / 09:48≈ on time ≈ +3 min
09:53≈ on time ≈ +3 min
09:56≈ on time ≈ +3 min
09: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 09:59No data—
Wed 4 NovTišnov 09:59No data—
Tue 3 NovTišnov 09:59No data—
Mon 2 NovTišnov 09:59No data—
Fri 30 OctTišnov 10:00No data—
Thu 29 OctTišnov 10:00No data—
Tue 27 OctTišnov 10:01No data—
Mon 26 OctTišnov 10:00No data—
Fri 23 OctTišnov 10:01No data—
Thu 22 OctTišnov 10:01No data—
Wed 21 OctTišnov 10:00No data—
Tue 20 OctTišnov 10:00No data—
Mon 19 OctTišnov 10:00No data—
Fri 16 OctTišnov 10:00No data—
Thu 15 OctTišnov 10:00No data—
Wed 14 OctTišnov 10:00No data—
Tue 13 OctTišnov 10:00No data—
Mon 12 OctTišnov 10:00No data—
Fri 9 OctTišnov 10:00No data—
Thu 8 OctTišnov 10:00No data—
Wed 7 OctTišnov 10:00No data—
Tue 6 OctTišnov 10:00No data—
Mon 5 Oct— 10:130 min+4 min
Fri 2 Oct— 10:140 min+2 min
Thu 1 Oct— 10:15+1 min+3 min
Wed 30 Sept— 10:140 min—
Tue 29 Sept— 12:240 min—
Fri 25 Sept— 10:12−1 min—
Thu 24 Sept— 10:140 min+2 min
Wed 23 Sept— 10:140 min—