Os 4444 4444 Brno hl. n. – Bohutice

View line Os 4444

Brno hl. n. 15:55 → Bohutice 16:50 Daily 0 h 55 min · 13 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Bohutice at 16:49 No data

  1. Brno hl. n.15:55
  2. Brno-Starý Lískovec16:03
  3. Troubsko16:07
  4. Střelice16:11
  5. Silůvky16:20
  6. Moravský Krumlov16:39
  7. Bohutice16:50

Next service: tomorrow 15:55 from Brno hl. n. · Tue 10 Nov

Next departure 15:55 tomorrow · Brno hl. n.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
55%
30/55 runs under 3 min
RT coverage: 55 full · 0 partial · 35 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+7min
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

  • Sat 29 Aug Max en route +18 min · last fix heading to — +17 min
  • Mon 17 Aug Max en route +13 min · last fix heading to — +11 min
  • Wed 26 Aug Max en route +9 min · last fix heading to — +9 min
  • Thu 20 Aug Max en route +9 min · last fix heading to — +8 min
  • Tue 18 Aug Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 55% · 30
  • 3–10 min 42% · 23
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 43% T n=7
  • 63% W n=8
  • 38% T n=8
  • 38% F n=8
  • 75% S n=8
  • 63% S n=8

Stops and timetable

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

Last 90 days, 55 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:55+1 min +8 min
15:59 / 16:00≈ +1 min ≈ +8 min
16:03 / 16:04≈ +1 min ≈ +7 min
16:06≈ +2 min ≈ +7 min
16:07≈ +2 min ≈ +7 min
16:08 / 16:09≈ +2 min ≈ +7 min
16:11 / 16:12≈ +2 min ≈ +7 min
16:15 / 16:16≈ +2 min ≈ +7 min
16:20 / 16:21≈ +2 min ≈ +7 min
16:25 / 16:29≈ +2 min ≈ +7 min
16:39 / 16:40≈ +2 min ≈ +7 min
16:44 / 16:45≈ +2 min ≈ +7 min
16:50+2 min +7 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
Mon 9 NovBohutice 16:49No data—
Sun 8 NovBohutice 16:49No data—
Sat 7 NovBohutice 16:49No data—
Fri 6 NovBohutice 16:49No data—
Thu 5 NovBohutice 16:49No data—
Wed 4 NovBohutice 16:49No data—
Tue 3 NovBohutice 16:49No data—
Mon 2 NovBohutice 16:49No data—
Sun 1 NovBohutice 16:51No data—
Sat 31 OctBohutice 16:51No data—
Fri 30 OctBohutice 16:51No data—
Thu 29 OctBohutice 16:51No data—
Wed 28 OctBohutice 16:51No data—
Tue 27 OctBohutice 16:51No data—
Mon 26 OctBohutice 16:51No data—
Sun 25 OctBohutice 16:51No data—
Sat 24 OctBohutice 16:51No data—
Fri 23 OctBohutice 16:51No data—
Thu 22 OctBohutice 16:51No data—
Wed 21 OctBohutice 16:51No data—
Tue 20 OctBohutice 16:51No data—
Mon 19 OctBohutice 16:51No data—
Sun 18 OctBohutice 16:51No data—
Sat 17 OctBohutice 16:51No data—
Fri 16 OctBohutice 16:51No data—
Thu 15 OctBohutice 16:51No data—
Wed 14 OctBohutice 16:51No data—
Tue 13 OctBohutice 16:51No data—
Mon 12 OctBohutice 16:51No data—
Sun 11 OctBohutice 16:51No data—