Os 13515 13515 Vrbno pod Pradědem – Milotice nad Opavou

View line Os 13515

Vrbno pod Pradědem 15:59 → Milotice nad Opavou 16:35 Daily 0 h 36 min · 10 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 15:59 from Vrbno pod Pradědem · Thu 5 Nov

Next departure 15:59 today · Vrbno pod Pradědem
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
93%
55/59 runs under 3 min
RT coverage: 59 full · 0 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Milotice nad Opavou, in minutes. One bar per run.

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

Worst days

  • Wed 12 Aug Max en route +4 min · last fix heading to — +4 min
  • Tue 11 Aug Max en route +4 min · last fix heading to — +4 min
  • Thu 3 Sept Max en route +3 min · last fix heading to — +3 min
  • Mon 17 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 10% · 6
  • On time 83% · 49
  • 3–10 min 7% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 88% T n=8
  • 88% W n=8
  • 88% T n=8
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 59 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
15:59on time +1 min
16:01≈ on time ≈ +1 min
16:04 / 16:05≈ on time ≈ +1 min
16:07≈ on time ≈ +1 min
16:13≈ on time ≈ +1 min
16:16≈ on time ≈ +1 min
16:19≈ on time ≈ +1 min
16:23 / 16:25≈ on time ≈ +1 min
16:27≈ on time ≈ +1 min
16:35on time +1 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
Wed 4 NovMilotice nad Opavou 16:34No data—
Tue 3 NovMilotice nad Opavou 16:34No data—
Mon 2 NovMilotice nad Opavou 16:34No data—
Sun 1 NovMilotice nad Opavou 16:36No data—
Sat 31 OctMilotice nad Opavou 16:36No data—
Fri 30 OctMilotice nad Opavou 16:36No data—
Thu 29 OctMilotice nad Opavou 16:36No data—
Wed 28 OctMilotice nad Opavou 16:36No data—
Tue 27 OctMilotice nad Opavou 16:36No data—
Mon 26 OctMilotice nad Opavou 16:36No data—
Sun 25 OctMilotice nad Opavou 16:36No data—
Sat 24 OctMilotice nad Opavou 16:36No data—
Fri 23 OctMilotice nad Opavou 16:36No data—
Thu 22 OctMilotice nad Opavou 16:36No data—
Wed 21 OctMilotice nad Opavou 16:36No data—
Tue 20 OctMilotice nad Opavou 16:36No data—
Mon 19 OctMilotice nad Opavou 16:36No data—
Sun 18 OctMilotice nad Opavou 16:36No data—
Sat 17 OctMilotice nad Opavou 16:36No data—
Fri 16 OctMilotice nad Opavou 16:36No data—
Thu 15 OctMilotice nad Opavou 16:36No data—
Wed 14 OctMilotice nad Opavou 16:36No data—
Tue 13 OctMilotice nad Opavou 16:36No data—
Mon 12 OctMilotice nad Opavou 16:36No data—
Sun 11 OctMilotice nad Opavou 16:36No data—
Sat 10 OctMilotice nad Opavou 16:36No data—
Fri 9 OctMilotice nad Opavou 16:36No data—
Thu 8 OctMilotice nad Opavou 16:36No data—
Wed 7 OctMilotice nad Opavou 16:36No data—
Tue 6 OctMilotice nad Opavou 16:36No data—