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

View line Os 4001

Brno hl. n. 04:35 → Sokolnice-Telnice 04:53 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Sokolnice-Telnice at 04:54 No data

  1. Brno hl. n.04:35
  2. Brno-Chrlice04:43
  3. Sokolnice-Telnice04:53

Next service: Monday 04:35 from Brno hl. n. · Mon 9 Nov

Next departure 04:35 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
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Sokolnice-Telnice, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 40
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
04:35on time +1 min
04:43 / 04:47≈ on time ≈ +1 min
04:53on time on time

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 NovSokolnice-Telnice 04:54No data—
Thu 5 NovSokolnice-Telnice 04:54No data—
Wed 4 NovSokolnice-Telnice 04:54No data—
Tue 3 NovSokolnice-Telnice 04:55No data—
Mon 2 NovSokolnice-Telnice 04:54No data—
Fri 30 OctSokolnice-Telnice 04:54No data—
Thu 29 OctSokolnice-Telnice 04:54No data—
Tue 27 OctSokolnice-Telnice 04:54No data—
Mon 26 OctSokolnice-Telnice 04:54No data—
Fri 23 OctSokolnice-Telnice 04:54No data—
Thu 22 OctSokolnice-Telnice 04:54No data—
Wed 21 OctSokolnice-Telnice 04:54No data—
Tue 20 OctSokolnice-Telnice 04:54No data—
Mon 19 OctSokolnice-Telnice 04:54No data—
Fri 16 OctSokolnice-Telnice 04:54No data—
Thu 15 OctSokolnice-Telnice 04:54No data—
Wed 14 OctSokolnice-Telnice 04:54No data—
Tue 13 OctSokolnice-Telnice 04:54No data—
Mon 12 OctSokolnice-Telnice 04:54No data—
Fri 9 OctSokolnice-Telnice 04:54No data—
Thu 8 OctSokolnice-Telnice 04:54No data—
Wed 7 OctSokolnice-Telnice 04:54No data—
Tue 6 OctSokolnice-Telnice 04:54No data—
Mon 5 Oct— 05:070 min—
Fri 2 Oct— 05:070 min—
Thu 1 Oct— 05:070 min—
Wed 30 Sept— 05:070 min—
Tue 29 Sept— 05:070 min—
Fri 25 Sept— 05:090 min+1 min
Thu 24 Sept— 05:070 min+1 min