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

View line Os 13403

Opava východ 04:41 → Hlučín 05:18 Daily 0 h 37 min · 10 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 04:41 from Opava východ · Sat 7 Nov

Next departure 04:41 today · Opava východ
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%
57/57 runs under 3 min
RT coverage: 57 full · 0 partial · 32 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

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

  • Early 0% · 0
  • On time 100% · 57
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 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, 57 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
04:41on time on time
04:43 / 04:44≈ on time ≈ on time
04:46≈ on time ≈ on time
04:50≈ on time ≈ on time
04:54 / 04:56≈ on time ≈ on time
05:00≈ on time ≈ on time
05:04 / 05:05≈ on time ≈ on time
05:08 / 05:09≈ on time ≈ on time
05:13≈ on time ≈ on time
05:18on 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
Fri 6 NovHlučín 05:19No data—
Thu 5 NovHlučín 05:19No data—
Wed 4 NovHlučín 05:19No data—
Tue 3 NovHlučín 05:20No data—
Mon 2 NovHlučín 05:19No data—
Sun 1 NovHlučín 05:19No data—
Sat 31 OctHlučín 05:19No data—
Fri 30 OctHlučín 05:19No data—
Thu 29 OctHlučín 05:19No data—
Wed 28 OctHlučín 05:20No data—
Tue 27 OctHlučín 05:19No data—
Mon 26 OctHlučín 05:19No data—
Sun 25 OctHlučín 05:19No data—
Sat 24 OctHlučín 05:19No data—
Fri 23 OctHlučín 05:19No data—
Thu 22 OctHlučín 05:19No data—
Wed 21 OctHlučín 05:19No data—
Tue 20 OctHlučín 05:19No data—
Mon 19 OctHlučín 05:19No data—
Sun 18 OctHlučín 05:19No data—
Sat 17 OctHlučín 05:19No data—
Fri 16 OctHlučín 05:19No data—
Thu 15 OctHlučín 05:19No data—
Wed 14 OctHlučín 05:19No data—
Tue 13 OctHlučín 05:19No data—
Mon 12 OctHlučín 05:19No data—
Sun 11 OctHlučín 05:19No data—
Sat 10 OctHlučín 05:19No data—
Fri 9 OctHlučín 05:19No data—
Thu 8 OctHlučín 05:19No data—