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.

✓ Today’s run finished

Today, last fix heading to Krnov at 04:59 No data

  1. Bruntál04:30
  2. Milotice nad Opavou04:40
  3. Zátor04:46
  4. Brantice04:50
  5. Krnov04:59

Next service: tomorrow 04:30 from Bruntál · Fri 20 Nov

Next departure 04:30 tomorrow · 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
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 31 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
Thu 19 NovKrnov 04:59No data—
Wed 18 NovKrnov 04:59No data—
Mon 16 NovKrnov 05:00No data—
Fri 13 NovKrnov 04:59No data—
Thu 12 NovKrnov 04:59No data—
Wed 11 NovKrnov 04:59No data—
Tue 10 NovKrnov 04:59No data—
Mon 9 NovKrnov 04:59No data—
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—