Os 13346 13346 Suchdol nad Odrou – Odry

View line Os 13346

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

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 21:10 from Suchdol nad Odrou · Sun 8 Nov

Next departure 21:10 today · Suchdol nad Odrou
On-time · 30 days
—
Too little data (0/24 runs with data)
RT coverage: 0 full · 0 partial · 24 no data
On-time · 90 days
61%
11/18 runs under 3 min
RT coverage: 18 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
P90
+11min
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

  • Sun 16 Aug Max en route +14 min · last fix heading to — +14 min
  • Sun 30 Aug Max en route +14 min · last fix heading to — +12 min
  • Thu 27 Aug Max en route +11 min · last fix heading to — +11 min
  • Mon 17 Aug Max en route +10 min · last fix heading to — +10 min
  • Sat 29 Aug Max en route +8 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 56% · 10
  • 3–10 min 17% · 3
  • 10–30 min 22% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 67% T n=3
  • 100% W n=3
  • 67% T n=3
  • — F n=0
  • 33% S n=3
  • 33% S n=3

Stops and timetable

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

Last 90 days, 18 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
21:10on time +12 min
21:16≈ on time ≈ +12 min
21:23on time +11 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
Sat 7 NovOdry 21:24No data—
Thu 5 NovOdry 21:24No data—
Wed 4 NovOdry 21:24No data—
Tue 3 NovOdry 21:24No data—
Mon 2 NovOdry 21:24No data—
Sun 1 NovOdry 21:24No data—
Sat 31 OctOdry 21:24No data—
Thu 29 OctOdry 21:24No data—
Wed 28 OctOdry 21:24No data—
Mon 26 OctOdry 21:24No data—
Sun 25 OctOdry 21:24No data—
Sat 24 OctOdry 21:24No data—
Thu 22 OctOdry 21:24No data—
Wed 21 OctOdry 21:24No data—
Tue 20 OctOdry 21:24No data—
Mon 19 OctOdry 21:25No data—
Sun 18 OctOdry 21:24No data—
Sat 17 OctOdry 21:24No data—
Thu 15 OctOdry 21:24No data—
Wed 14 OctOdry 21:24No data—
Tue 13 OctOdry 21:25No data—
Mon 12 OctOdry 21:25No data—
Sun 11 OctOdry 21:24No data—
Sat 10 OctOdry 21:24No data—
Thu 8 OctOdry 21:24No data—
Wed 7 OctOdry 21:24No data—
Tue 6 OctOdry 21:24No data—
Mon 5 OctOdry 21:24No data—
Mon 31 Aug— 21:380 min—
Sun 30 Aug— 21:50+12 min+14 min