Os 23311 23311 Bílovec – Studénka

View line Os 23311

Bílovec 08:30 → Studénka 08:42 Mon, Tue, Wed, Thu, Fri, Sat 0 h 12 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Studénka at 08:43 No data

  1. Bílovec08:30
  2. Velké Albrechtice08:32
  3. Studénka město08:39
  4. Studénka08:42

Next service: Monday 08:30 from Bílovec · Mon 16 Nov

Next departure 08:30 Monday · Bílovec
On-time · 30 days
—
Too little data (0/26 runs with data)
RT coverage: 0 full · 0 partial · 26 no data
On-time · 90 days
90%
38/42 runs under 3 min
RT coverage: 42 full · 0 partial · 35 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 Studénka, 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 3 Sept Max en route +18 min · last fix heading to — +18 min
  • Thu 20 Aug Max en route +8 min · last fix heading to — +7 min
  • Fri 4 Sept Max en route +4 min · last fix heading to — +4 min
  • Wed 26 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 38
  • 3–10 min 7% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 71% T n=7
  • 86% F n=7
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 42 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:30on time on time
08:32≈ on time ≈ +1 min
08:39≈ on time ≈ on time
08:42on 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
Sat 14 NovStudénka 08:43No data—
Fri 13 NovStudénka 08:43No data—
Thu 12 NovStudénka 08:43No data—
Wed 11 NovStudénka 08:43No data—
Tue 10 NovStudénka 08:43No data—
Mon 9 NovStudénka 08:43No data—
Sat 7 NovStudénka 08:43No data—
Fri 6 NovStudénka 08:43No data—
Thu 5 NovStudénka 08:43No data—
Wed 4 NovStudénka 08:43No data—
Tue 3 NovStudénka 08:43No data—
Mon 2 NovStudénka 08:43No data—
Sat 31 OctStudénka 08:43No data—
Fri 30 OctStudénka 08:43No data—
Thu 29 OctStudénka 08:43No data—
Wed 28 OctStudénka 08:43No data—
Tue 27 OctStudénka 08:43No data—
Mon 26 OctStudénka 08:43No data—
Sat 24 OctStudénka 08:43No data—
Fri 23 OctStudénka 08:43No data—
Thu 22 OctStudénka 08:44No data—
Wed 21 OctStudénka 08:43No data—
Tue 20 OctStudénka 08:43No data—
Mon 19 OctStudénka 08:43No data—
Sat 17 OctStudénka 08:43No data—
Fri 16 OctStudénka 08:44No data—
Thu 15 OctStudénka 08:43No data—
Wed 14 OctStudénka 08:43No data—
Tue 13 OctStudénka 08:43No data—
Mon 12 OctStudénka 08:43No data—