Os 4147 4147 Brno hl. n. – Nemotice

View line Os 4147

Brno hl. n. 13:43 → Nemotice 14:51 Mon, Tue, Wed, Thu, Fri 1 h 08 min · 16 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Nemotice at 14:52 No data

  1. Brno hl. n.13:43
  2. Šlapanice zastávka14:03
  3. Ponětovice14:07
  4. Slavkov u Brna14:19
  5. Marefy14:30
  6. Nesovice14:41
  7. Nemotice14:51

Next service: Monday 13:43 from Brno hl. n. · Mon 9 Nov

Next departure 13:43 Monday · 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
88%
15/17 runs under 3 min
RT coverage: 17 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

  • Mon 10 Aug Max en route +19 min · last fix heading to — +16 min
  • Fri 18 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 82% · 14
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 67% 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, 17 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
13:43on time +1 min
13:47 / 13:50≈ on time ≈ +1 min
13:56 / 14:00≈ on time ≈ +1 min
14:03 / 14:04≈ on time ≈ +1 min
14:05≈ on time ≈ +1 min
14:07≈ on time ≈ +2 min
14:11≈ on time ≈ +2 min
14:15 / 14:16≈ on time ≈ +2 min
14:19 / 14:22≈ on time ≈ +2 min
14:26 / 14:27≈ on time ≈ +2 min
14:30≈ on time ≈ +2 min
14:33 / 14:34≈ on time ≈ +2 min
14:38≈ on time ≈ +2 min
14:41 / 14:42≈ on time ≈ +2 min
14:47≈ on time ≈ +3 min
14:51on 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
Fri 6 NovNemotice 14:52No data—
Thu 5 NovNemotice 14:52No data—
Wed 4 NovNemotice 14:53No data—
Tue 3 NovNemotice 14:52No data—
Mon 2 NovNemotice 14:52No data—
Fri 30 OctNemotice 14:52No data—
Thu 29 OctNemotice 14:52No data—
Tue 27 OctNemotice 14:52No data—
Mon 26 OctNemotice 14:52No data—
Fri 23 OctNemotice 14:52No data—
Thu 22 OctNemotice 14:52No data—
Wed 21 OctNemotice 14:52No data—
Tue 20 OctNemotice 14:52No data—
Mon 19 OctNemotice 14:52No data—
Fri 16 OctNemotice 14:52No data—
Thu 15 OctNemotice 14:52No data—
Wed 14 OctNemotice 14:52No data—
Tue 13 OctNemotice 14:52No data—
Mon 12 OctNemotice 14:52No data—
Fri 9 OctNemotice 14:52No data—
Thu 8 OctNemotice 14:52No data—
Wed 7 OctNemotice 14:52No data—
Tue 6 OctNemotice 14:52No data—
Mon 5 Oct— 15:050 min+2 min
Fri 2 Oct— 15:07+1 min+3 min
Thu 1 Oct— 15:060 min—
Wed 30 Sept— 15:07+1 min+2 min
Tue 29 Sept— 15:06+1 min+3 min
Fri 25 Sept— 15:050 min+4 min
Thu 24 Sept— 15:07+1 min+3 min