Os 4155 4155 Brno hl. n. – Nemotice

View line Os 4155

Brno hl. n. 17:41 → Nemotice 18:52 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 16 stops České dráhy, a.s.

Running now · updated 18:52

Between Brankovice and Nemotice No data

Estimated arrival at Nemotice 18:52 · 49 km/h

  1. Brno hl. n.17:41
  2. Šlapanice zastávka18:04
  3. Ponětovice18:08
  4. Slavkov u Brna18:20
  5. Marefy18:30
  6. Brankovice18:47
  7. Nemotice18:52
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
81%
13/16 runs under 3 min
RT coverage: 16 full · 0 partial · 23 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 Nemotice, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 11 Aug Max en route +7 min · last fix heading to — +4 min
  • Tue 29 Sept Max en route +4 min · last fix heading to — +3 min
  • Tue 22 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 13
  • 3–10 min 19% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 0% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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 10Today
17:41on time +1 minPassed
17:45 / 17:49≈ on time ≈ +1 minPassed
18:00 / 18:01≈ +1 min ≈ +1 minPassed
18:04 / 18:05≈ +1 min ≈ +1 minPassed
18:06≈ +1 min ≈ +1 minPassed
18:08≈ +1 min ≈ +1 minPassed
18:11≈ +1 min ≈ +2 minPassed
18:16≈ +1 min ≈ +2 minPassed
18:20 / 18:22≈ on time ≈ +2 minPassed
18:26 / 18:27≈ on time ≈ +2 minPassed
18:30≈ on time ≈ +2 minPassed
18:33 / 18:34≈ on time ≈ +2 minPassed
18:38≈ on time ≈ +2 minPassed
18:42≈ on time ≈ +3 minPassed
18:47 / 18:48≈ on time ≈ +3 minPassed
18:52on time +3 minNext

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 NovNemotice 18:49No data—
Wed 4 NovNemotice 18:53No data—
Tue 3 NovNemotice 18:53No data—
Mon 2 NovNemotice 18:53No data—
Fri 30 OctKyjov 19:06No data—
Thu 29 OctNemotice 18:53No data—
Tue 27 OctKyjov 19:07No data—
Mon 26 OctNemotice 18:53No data—
Fri 23 OctKyjov 19:07No data—
Thu 22 OctNemotice 18:53No data—
Wed 21 OctNemotice 18:53No data—
Tue 20 OctNemotice 18:54No data—
Mon 19 OctNemotice 18:53No data—
Fri 16 OctKyjov 19:06No data—
Thu 15 OctNemotice 18:53No data—
Wed 14 OctNemotice 18:53No data—
Tue 13 OctNemotice 18:53No data—
Mon 12 OctNemotice 18:54No data—
Fri 9 OctKyjov 19:06No data—
Thu 8 OctNemotice 18:53No data—
Wed 7 OctNemotice 18:53No data—
Tue 6 OctNemotice 18:53No data—
Mon 5 OctNemotice 18:53No data—
Fri 2 Oct— 19:190 min+1 min
Thu 1 Oct— 19:06−1 min+1 min
Wed 30 Sept— 19:070 min+2 min
Tue 29 Sept— 19:09+3 min+4 min
Fri 25 Sept— 19:22+2 min+3 min
Thu 24 Sept— 19:08+2 min+2 min
Wed 23 Sept— 19:06−1 min+2 min