Os 13342 13342 Suchdol nad Odrou – Odry

View line Os 13342

Suchdol nad Odrou 08:10 → Odry 08:23 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Odry at 08:24 No data

  1. Suchdol nad Odrou08:10
  2. Mankovice08:16
  3. Odry08:23

Next service: tomorrow 08:10 from Suchdol nad Odrou · Fri 6 Nov

Next departure 08:10 tomorrow · Suchdol nad Odrou
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
80%
32/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Odry, in minutes. One bar per run.

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

Worst days

  • Thu 20 Aug Max en route +7 min · last fix heading to — +7 min
  • Tue 11 Aug Max en route +7 min · last fix heading to — +7 min
  • Mon 17 Aug Max en route +5 min · last fix heading to — +5 min
  • Thu 13 Aug Max en route +5 min · last fix heading to — +5 min
  • Wed 12 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 78% · 31
  • 3–10 min 20% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 88% T n=8
  • 75% W n=8
  • 63% T n=8
  • 88% 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
08:10on time +5 min
08:16≈ on time ≈ +5 min
08:23on time +5 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
Thu 5 NovOdry 08:24No data—
Wed 4 NovOdry 08:24No data—
Tue 3 NovOdry 08:24No data—
Mon 2 NovOdry 08:24No data—
Fri 30 OctOdry 08:24No data—
Thu 29 OctOdry 08:24No data—
Tue 27 OctOdry 08:24No data—
Mon 26 OctOdry 08:24No data—
Fri 23 OctOdry 08:24No data—
Thu 22 OctOdry 08:25No data—
Wed 21 OctOdry 08:24No data—
Tue 20 OctOdry 08:24No data—
Mon 19 OctOdry 08:24No data—
Fri 16 OctOdry 08:24No data—
Thu 15 OctOdry 08:24No data—
Wed 14 OctOdry 08:24No data—
Tue 13 OctOdry 08:24No data—
Mon 12 OctOdry 08:24No data—
Fri 9 OctOdry 08:24No data—
Thu 8 OctOdry 08:24No data—
Wed 7 OctOdry 08:24No data—
Tue 6 OctOdry 08:24No data—
Mon 5 Oct— 08:39+2 min+2 min
Fri 2 Oct— 08:40+2 min+2 min
Thu 1 Oct— 08:380 min—
Wed 30 Sept— 08:380 min—
Tue 29 Sept— 08:370 min—
Fri 25 Sept— 08:380 min—
Thu 24 Sept— 08:380 min—
Wed 23 Sept— 08:380 min—