R 341 341 Ostrava-Svinov – Čadca

View line R 341

Ostrava-Svinov 05:41 → Čadca 06:59 Daily 1 h 18 min · 23 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Čadca at 06:59 No data

  1. Ostrava-Svinov05:41
  2. Dolní Lutyně06:01
  3. Louky nad Olší06:19
  4. Třinec-Konská (Trzyniec-Końska)06:29
  5. Bystřice06:36
  6. Bocanovice06:44
  7. Čadca06:59

Next service: tomorrow 05:41 from Ostrava-Svinov · Mon 9 Nov

Next departure 05:41 tomorrow · Ostrava-Svinov
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
55%
31/56 runs under 3 min
RT coverage: 56 full · 0 partial · 34 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Čadca, 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 26 Aug Max en route +42 min · last fix heading to — +37 min
  • Fri 21 Aug Max en route +11 min · last fix heading to — +9 min
  • Mon 17 Aug Max en route +10 min · last fix heading to — +9 min
  • Tue 29 Sept Max en route +9 min · last fix heading to — +8 min
  • Fri 11 Sept Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 55% · 31
  • 3–10 min 43% · 24
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 38% M n=8
  • 50% T n=8
  • 50% W n=8
  • 38% T n=8
  • 63% F n=8
  • 75% S n=8
  • 75% S n=8

Stops and timetable

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

Last 90 days, 56 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
05:41+3 min +7 min
05:44≈ +3 min ≈ +7 min
05:47 / 05:49≈ +3 min ≈ +7 min
05:56 / 05:59≈ +3 min ≈ +7 min
06:01≈ +2 min ≈ +7 min
06:05≈ +2 min ≈ +7 min
06:08 / 06:10≈ +2 min ≈ +7 min
06:19≈ +2 min ≈ +7 min
06:20≈ +3 min ≈ +7 min
06:24 / 06:26≈ +2 min ≈ +7 min
06:28≈ +2 min ≈ +7 min
06:29≈ +2 min ≈ +7 min
06:30≈ +2 min ≈ +7 min
06:32 / 06:33≈ +2 min ≈ +7 min
06:35≈ +2 min ≈ +7 min
06:36≈ +2 min ≈ +7 min
06:38≈ +2 min ≈ +7 min
06:40 / 06:41≈ +2 min ≈ +7 min
06:44≈ +2 min ≈ +7 min
06:48≈ +2 min ≈ +7 min
06:49≈ +2 min ≈ +7 min
06:53≈ +2 min ≈ +7 min
06:59+2 min +8 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
Sun 8 NovČadca 06:59No data—
Sat 7 NovČadca 06:59No data—
Fri 6 NovČadca 06:59No data—
Thu 5 NovČadca 06:59No data—
Wed 4 NovČadca 06:59No data—
Tue 3 NovČadca 06:59No data—
Mon 2 NovČadca 06:59No data—
Sun 1 NovČadca 07:00No data—
Sat 31 OctČadca 07:00No data—
Fri 30 OctČadca 07:00No data—
Thu 29 OctČadca 07:00No data—
Wed 28 OctČadca 07:00No data—
Tue 27 OctČadca 07:00No data—
Mon 26 OctČadca 07:00No data—
Sun 25 OctČadca 07:00No data—
Sat 24 OctČadca 07:00No data—
Fri 23 OctČadca 07:00No data—
Thu 22 OctČadca 07:00No data—
Wed 21 OctČadca 07:00No data—
Tue 20 OctČadca 07:00No data—
Mon 19 OctČadca 07:00No data—
Sun 18 OctČadca 07:00No data—
Sat 17 OctČadca 07:00No data—
Fri 16 OctČadca 07:00No data—
Thu 15 OctČadca 07:00No data—
Wed 14 OctČadca 07:00No data—
Tue 13 OctČadca 07:00No data—
Mon 12 OctČadca 07:00No data—
Sun 11 OctČadca 07:00No data—
Sat 10 OctČadca 07:00No data—