Os 13432 13432 Hlučín – Opava východ

View line Os 13432

Hlučín 20:31 → Opava východ 21:12 Daily 0 h 41 min · 10 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Tuesday 10 November No data

Next service: today 20:31 from Hlučín · Wed 11 Nov

Next departure 20:31 today · Hlučín
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
100%
52/52 runs under 3 min
RT coverage: 52 full · 0 partial · 37 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 Opava východ, 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

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

  • Early 19% · 10
  • On time 81% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 52 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
20:31on time on time
20:35≈ on time ≈ on time
20:39 / 20:40≈ on time ≈ on time
20:44≈ on time ≈ on time
20:48 / 20:49≈ on time ≈ on time
20:53 / 20:58≈ on time ≈ on time
21:02≈ on time ≈ on time
21:05 / 21:06≈ on time ≈ on time
21:08≈ on time ≈ on time
21:12on 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
Tue 10 NovOpava východ 21:14No data—
Mon 9 NovOpava východ 21:13No data—
Sun 8 NovOpava východ 21:13No data—
Sat 7 NovOpava východ 21:13No data—
Fri 6 NovOpava východ 21:13No data—
Thu 5 NovOpava východ 21:13No data—
Wed 4 NovOpava východ 21:13No data—
Tue 3 NovOpava východ 21:13No data—
Mon 2 NovOpava východ 21:13No data—
Sun 1 NovOpava východ 21:13No data—
Sat 31 OctOpava východ 21:13No data—
Fri 30 OctOpava východ 21:13No data—
Thu 29 OctOpava východ 21:13No data—
Wed 28 OctOpava východ 21:13No data—
Tue 27 OctOpava východ 21:14No data—
Mon 26 OctOpava východ 21:13No data—
Sun 25 OctOpava východ 21:13No data—
Sat 24 OctOpava východ 21:13No data—
Fri 23 OctOpava východ 21:13No data—
Thu 22 OctOpava východ 21:13No data—
Wed 21 OctOpava východ 21:13No data—
Tue 20 OctOpava východ 21:13No data—
Mon 19 OctOpava východ 21:14No data—
Sun 18 OctOpava východ 21:13No data—
Sat 17 OctOpava východ 21:13No data—
Fri 16 OctOpava východ 21:13No data—
Thu 15 OctOpava východ 21:13No data—
Wed 14 OctOpava východ 21:13No data—
Tue 13 OctOpava východ 21:13No data—
Mon 12 OctOpava východ 21:14No data—