Os 4443 4443 Bohutice – Brno hl. n.

View line Os 4443

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 15:59 from Bohutice · Thu 5 Nov

Next departure 15:59 today · Bohutice
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
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 21 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 Brno hl. n., 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 26 Aug Max en route +7 min · last fix heading to — +5 min
  • Mon 17 Aug Max en route +8 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 18% · 7
  • On time 78% · 31
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Last 90 days, 41 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:59on time +2 min
16:03 / 16:04≈ on time ≈ +2 min
16:08 / 16:17≈ on time ≈ +2 min
16:28 / 16:31≈ on time ≈ +1 min
16:35 / 16:36≈ on time ≈ +1 min
16:39 / 16:40≈ on time ≈ +1 min
16:44 / 16:45≈ on time ≈ +1 min
16:47 / 16:48≈ on time ≈ +1 min
16:49≈ on time ≈ +2 min
16:50≈ on time ≈ +2 min
16:52 / 16:53≈ on time ≈ +2 min
16:56 / 17:00≈ on time ≈ +2 min
17:05on 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
Wed 4 NovBrno hl. n. 17:04No data—
Tue 3 NovBrno hl. n. 17:04No data—
Mon 2 NovBrno hl. n. 17:04No data—
Fri 30 OctBrno hl. n. 17:06No data—
Thu 29 OctBrno hl. n. 17:06No data—
Tue 27 OctBrno hl. n. 17:07No data—
Mon 26 OctBrno hl. n. 17:06No data—
Fri 23 OctBrno hl. n. 17:06No data—
Thu 22 OctBrno hl. n. 17:06No data—
Wed 21 OctBrno hl. n. 17:06No data—
Tue 20 OctBrno hl. n. 17:06No data—
Mon 19 OctBrno hl. n. 17:06No data—
Fri 16 OctBrno hl. n. 17:06No data—
Thu 15 OctBrno hl. n. 17:06No data—
Wed 14 OctBrno hl. n. 17:06No data—
Tue 13 OctBrno hl. n. 17:06No data—
Mon 12 OctBrno hl. n. 17:06No data—
Fri 9 OctBrno hl. n. 17:06No data—
Thu 8 OctBrno hl. n. 17:06No data—
Wed 7 OctBrno hl. n. 17:06No data—
Tue 6 OctBrno hl. n. 17:06No data—
Mon 5 OctBrno hl. n. 17:060 min+2 min
Fri 2 Oct— 17:20+1 min+4 min
Thu 1 Oct— 17:18−1 min—
Wed 30 Sept— 17:19−1 min+2 min
Tue 29 Sept— 17:18−1 min—
Fri 25 Sept— 17:21+1 min+3 min
Thu 24 Sept— 17:17−2 min+2 min
Wed 23 Sept— 17:18−2 min+2 min
Tue 22 Sept— 17:18−2 min+2 min