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

View line Os 13411

Opava východ 08:42 → Hlučín 09:19 Daily 0 h 37 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Hlučín at 09:19 No data

  1. Opava východ08:42
  2. Malé Hoštice08:47
  3. Velké Hoštice08:51
  4. Kravaře-Kouty09:01
  5. Dolní Benešov - Zábřeh09:05
  6. Kozmice09:14
  7. Hlučín09:19

Next service: tomorrow 08:42 from Opava východ · Fri 13 Nov

Next departure 08:42 tomorrow · Opava východ
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
100%
52/52 runs under 3 min
RT coverage: 52 full · 0 partial · 38 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 Hlučín, 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 0% · 0
  • On time 100% · 52
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 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
08:42on time on time
08:44 / 08:45≈ on time ≈ on time
08:47≈ on time ≈ on time
08:51≈ on time ≈ on time
08:55 / 08:57≈ on time ≈ on time
09:01≈ on time ≈ on time
09:05 / 09:06≈ on time ≈ on time
09:09 / 09:10≈ on time ≈ on time
09:14≈ on time ≈ on time
09:19on 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 12 NovHlučín 09:19No data—
Wed 11 NovHlučín 09:19No data—
Tue 10 NovHlučín 09:19No data—
Mon 9 NovHlučín 09:19No data—
Sun 8 NovHlučín 09:19No data—
Sat 7 NovHlučín 09:20No data—
Fri 6 NovHlučín 09:19No data—
Thu 5 NovHlučín 09:19No data—
Wed 4 NovHlučín 09:19No data—
Tue 3 NovHlučín 09:19No data—
Mon 2 NovHlučín 09:19No data—
Sun 1 NovHlučín 09:20No data—
Sat 31 OctHlučín 09:20No data—
Fri 30 OctHlučín 09:20No data—
Thu 29 OctHlučín 09:20No data—
Wed 28 OctHlučín 09:20No data—
Tue 27 OctHlučín 09:20No data—
Mon 26 OctHlučín 09:20No data—
Sun 25 OctHlučín 09:20No data—
Sat 24 OctHlučín 09:20No data—
Fri 23 OctHlučín 09:21No data—
Thu 22 OctHlučín 09:21No data—
Wed 21 OctHlučín 09:20No data—
Tue 20 OctHlučín 09:20No data—
Mon 19 OctHlučín 09:20No data—
Sun 18 OctHlučín 09:20No data—
Sat 17 OctHlučín 09:20No data—
Fri 16 OctHlučín 09:21No data—
Thu 15 OctHlučín 09:20No data—
Wed 14 OctHlučín 09:20No data—