Os 4032 4032 Sokolnice-Telnice – Brno hl. n.

View line Os 4032

Sokolnice-Telnice 21:10 → Brno hl. n. 21:26 Daily 0 h 16 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Brno hl. n. at 21:27 No data

  1. Sokolnice-Telnice21:10
  2. Brno-Chrlice21:15
  3. Brno hl. n.21:26

Next service: tomorrow 21:10 from Sokolnice-Telnice · Sun 15 Nov

Next departure 21:10 tomorrow · Sokolnice-Telnice
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
94%
46/49 runs under 3 min
RT coverage: 49 full · 0 partial · 41 no data
Typical delay
−1min
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 30 Sept Max en route +6 min · last fix heading to — +5 min
  • Thu 10 Sept Max en route +14 min · last fix heading to — +3 min
  • Fri 28 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 14% · 7
  • On time 80% · 39
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 86% T n=7
  • 86% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 49 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
21:105 min early on time
21:15 / 21:16≈ 4 min early ≈ on time
21:261 min early +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
Sat 14 NovBrno hl. n. 21:27No data—
Fri 13 NovSkalice n. Svit. 22:19No data—
Thu 12 NovSkalice n. Svit. 22:19No data—
Wed 11 NovSkalice n. Svit. 22:19No data—
Tue 10 NovSkalice n. Svit. 22:19No data—
Mon 9 NovSkalice n. Svit. 22:19No data—
Sun 8 NovBrno hl. n. 21:27No data—
Sat 7 NovBrno hl. n. 21:27No data—
Fri 6 NovSkalice n. Svit. 22:19No data—
Thu 5 NovSkalice n. Svit. 22:19No data—
Wed 4 NovSkalice n. Svit. 22:19No data—
Tue 3 NovSkalice n. Svit. 22:19No data—
Mon 2 NovSkalice n. Svit. 22:19No data—
Sun 1 NovBrno hl. n. 21:27No data—
Sat 31 OctBrno hl. n. 21:27No data—
Fri 30 OctSkalice n. Svit. 22:21No data—
Thu 29 OctSkalice n. Svit. 22:21No data—
Wed 28 OctBrno hl. n. 21:27No data—
Tue 27 OctSkalice n. Svit. 22:22No data—
Mon 26 OctSkalice n. Svit. 22:21No data—
Sun 25 OctBrno hl. n. 21:27No data—
Sat 24 OctBrno hl. n. 21:27No data—
Fri 23 OctSkalice n. Svit. 22:21No data—
Thu 22 OctSkalice n. Svit. 22:21No data—
Wed 21 OctSkalice n. Svit. 22:21No data—
Tue 20 OctSkalice n. Svit. 22:21No data—
Mon 19 OctSkalice n. Svit. 22:22No data—
Sun 18 OctBrno hl. n. 21:27No data—
Sat 17 OctBrno hl. n. 21:27No data—
Fri 16 OctSkalice n. Svit. 22:21No data—