Os 4426 4426 Brno hl. n. – Bohutice

View line Os 4426

Brno hl. n. 05:49 → Bohutice 06:58 Mon, Tue, Wed, Thu, Fri 1 h 09 min · 13 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Bohutice at 06:59 No data

  1. Brno hl. n.05:49
  2. Brno-Starý Lískovec06:01
  3. Troubsko06:05
  4. Střelice06:09
  5. Silůvky06:21
  6. Moravský Krumlov06:39
  7. Bohutice06:58

Next service: tomorrow 05:49 from Brno hl. n. · Wed 11 Nov

Next departure 05:49 tomorrow · Brno hl. n.
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
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Bohutice, 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 19 Aug Max en route +12 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 36
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 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 (13 stops).

Last 90 days, 37 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:49+1 min +3 min
05:53 / 05:57≈ +1 min ≈ +3 min
06:01≈ +1 min ≈ +2 min
06:04≈ +1 min ≈ +2 min
06:05≈ +1 min ≈ +2 min
06:06 / 06:07≈ +1 min ≈ +2 min
06:09 / 06:13≈ +1 min ≈ +2 min
06:16 / 06:17≈ +1 min ≈ +2 min
06:21 / 06:22≈ +1 min ≈ +2 min
06:26 / 06:29≈ on time ≈ +2 min
06:39 / 06:48≈ on time ≈ +1 min
06:53≈ on time ≈ +2 min
06:58on time +2 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
Tue 10 NovBohutice 06:59No data—
Mon 9 NovBohutice 06:59No data—
Fri 6 NovBohutice 06:59No data—
Thu 5 NovBohutice 06:59No data—
Wed 4 NovBohutice 06:59No data—
Tue 3 NovBohutice 06:59No data—
Mon 2 NovBohutice 06:59No data—
Fri 30 OctBohutice 06:59No data—
Thu 29 OctBohutice 06:59No data—
Tue 27 OctBohutice 06:59No data—
Mon 26 OctBohutice 06:59No data—
Fri 23 OctBohutice 06:59No data—
Thu 22 OctBohutice 06:59No data—
Wed 21 OctBohutice 06:59No data—
Tue 20 OctBohutice 06:59No data—
Mon 19 OctBohutice 06:59No data—
Fri 16 OctBohutice 06:59No data—
Thu 15 OctBohutice 06:59No data—
Wed 14 OctBohutice 06:59No data—
Tue 13 OctBohutice 06:59No data—
Mon 12 OctBohutice 06:59No data—
Fri 9 OctBohutice 06:59No data—
Thu 8 OctBohutice 06:59No data—
Wed 7 OctBohutice 06:59No data—
Tue 6 OctBohutice 06:59No data—
Mon 5 Oct— 07:130 min+2 min
Fri 2 Oct— 07:130 min+3 min
Thu 1 Oct— 07:130 min+2 min
Wed 30 Sept— 07:120 min+2 min
Tue 29 Sept— 07:14+2 min+2 min