Os 4019 4019 Rájec-Jestřebí – Brno hl. n.

View line Os 4019

Rájec-Jestřebí 11:53 → Brno hl. n. 12:29 Daily 0 h 36 min · 10 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Tuesday 17 November No data

Next service: today 11:53 from Rájec-Jestřebí · Wed 18 Nov

Next departure 11:53 today · Rájec-Jestřebí
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 full · 0 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

  • Tue 1 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 27% · 12
  • On time 71% · 32
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 83% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 45 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
11:53on time +2 min
11:55 / 11:56≈ on time ≈ +2 min
11:58 / 11:59≈ on time ≈ +2 min
12:00 / 12:01≈ on time ≈ +2 min
12:07≈ on time ≈ +1 min
12:09 / 12:10≈ on time ≈ +1 min
12:12≈ on time ≈ +1 min
12:16 / 12:17≈ on time ≈ +1 min
12:22 / 12:25≈ on time ≈ +1 min
12:29on time +1 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 17 NovBrno hl. n. 12:29No data—
Mon 16 NovBrno-Chrlice 12:39No data—
Sun 15 NovBrno hl. n. 12:30No data—
Sat 14 NovBrno hl. n. 12:29No data—
Fri 13 NovBrno-Chrlice 12:39No data—
Thu 12 NovBrno-Chrlice 12:39No data—
Wed 11 NovBrno-Chrlice 12:39No data—
Tue 10 NovBrno-Chrlice 12:39No data—
Mon 9 NovBrno-Chrlice 12:39No data—
Sun 8 NovBrno hl. n. 12:29No data—
Sat 7 NovBrno hl. n. 12:29No data—
Fri 6 NovBrno-Chrlice 12:39No data—
Thu 5 NovBrno-Chrlice 12:39No data—
Wed 4 NovBrno-Chrlice 12:39No data—
Tue 3 NovBrno-Chrlice 12:39No data—
Mon 2 NovBrno-Chrlice 12:39No data—
Sun 1 NovBrno hl. n. 12:30No data—
Sat 31 OctBrno hl. n. 12:30No data—
Fri 30 OctBrno-Chrlice 12:40No data—
Thu 29 OctBrno-Chrlice 12:40No data—
Wed 28 OctBrno hl. n. 12:30No data—
Tue 27 OctBrno-Chrlice 12:40No data—
Mon 26 OctBrno-Chrlice 12:40No data—
Sun 25 OctBrno hl. n. 12:30No data—
Sat 24 OctBrno hl. n. 12:30No data—
Fri 23 OctBrno-Chrlice 12:40No data—
Thu 22 OctBrno-Chrlice 12:40No data—
Wed 21 OctBrno-Chrlice 12:40No data—
Tue 20 OctBrno-Chrlice 12:40No data—
Mon 19 OctBrno-Chrlice 12:40No data—