Os 3501 3501 Bruntál – Krnov

View line Os 3501

Bruntál 04:30 → Krnov 04:59 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 04:30 from Bruntál · Mon 9 Nov

Next departure 04:30 Monday · Bruntál
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
98%
39/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 Krnov, 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 19 Aug Max en route +12 min · last fix heading to — +12 min

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 98% · 39
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 88% 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 (5 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:30on time on time
04:40 / 04:41≈ on time ≈ on time
04:46≈ on time ≈ on time
04:50 / 04:51≈ on time ≈ on time
04:59on 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 NovKrnov 04:59No data—
Thu 5 NovKrnov 04:59No data—
Wed 4 NovKrnov 04:59No data—
Tue 3 NovKrnov 04:59No data—
Mon 2 NovKrnov 04:59No data—
Fri 30 OctKrnov 05:00No data—
Thu 29 OctKrnov 05:00No data—
Tue 27 OctKrnov 05:00No data—
Mon 26 OctKrnov 05:00No data—
Fri 23 OctKrnov 05:00No data—
Thu 22 OctKrnov 05:00No data—
Wed 21 OctKrnov 05:00No data—
Tue 20 OctKrnov 05:00No data—
Mon 19 OctKrnov 05:00No data—
Fri 16 OctKrnov 05:00No data—
Thu 15 OctKrnov 05:00No data—
Wed 14 OctKrnov 05:00No data—
Tue 13 OctKrnov 05:00No data—
Mon 12 OctKrnov 05:00No data—
Fri 9 OctKrnov 05:00No data—
Thu 8 OctKrnov 05:00No data—
Wed 7 OctKrnov 05:00No data—
Tue 6 OctKrnov 05:00No data—
Mon 5 Oct— 05:140 min—
Fri 2 Oct— 05:130 min—
Thu 1 Oct— 05:140 min—
Wed 30 Sept— 05:140 min—
Tue 29 Sept— 05:130 min+1 min
Fri 25 Sept— 05:140 min—
Thu 24 Sept— 05:130 min—