Os 13711 13711 Olomouc hl. n. – Šternberk

View line Os 13711

Olomouc hl. n. 13:10 → Šternberk 13:25 Mon, Tue, Wed, Thu, Fri 0 h 15 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:10 from Olomouc hl. n. · Mon 9 Nov

Next departure 13:10 today · Olomouc hl. n.
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 23 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 Šternberk, in minutes. One bar per run.

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

Worst days

  • Thu 10 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
13:10on time on time
13:14≈ on time ≈ on time
13:17 / 13:18≈ on time ≈ on time
13:21≈ on time ≈ on time
13:25on 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 NovŠternberk 13:24No data—
Thu 5 NovŠternberk 13:24No data—
Wed 4 NovŠternberk 13:24No data—
Tue 3 NovŠternberk 13:24No data—
Mon 2 NovŠternberk 13:24No data—
Fri 30 OctŠternberk 13:26No data—
Thu 29 OctŠternberk 13:26No data—
Tue 27 OctŠternberk 13:26No data—
Mon 26 OctŠternberk 13:26No data—
Fri 23 OctŠternberk 13:26No data—
Thu 22 OctŠternberk 13:26No data—
Wed 21 OctŠternberk 13:26No data—
Tue 20 OctŠternberk 13:26No data—
Mon 19 OctŠternberk 13:26No data—
Fri 16 OctŠternberk 13:26No data—
Thu 15 OctŠternberk 13:26No data—
Wed 14 OctŠternberk 13:26No data—
Tue 13 OctŠternberk 13:26No data—
Mon 12 OctŠternberk 13:26No data—
Fri 9 OctŠternberk 13:26No data—
Thu 8 OctŠternberk 13:26No data—
Wed 7 OctŠternberk 13:26No data—
Tue 6 OctŠternberk 13:26No data—
Mon 5 Oct— 13:400 min—
Fri 2 Oct— 13:400 min—
Thu 1 Oct— 13:39−1 min—
Wed 30 Sept— 13:390 min—
Tue 29 Sept— 13:390 min—
Fri 25 Sept— 13:38−1 min—
Thu 24 Sept— 13:400 min—