Os 23303 23303 Bílovec – Studénka

View line Os 23303

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

✓ Today’s run finished

Today, last fix heading to Studénka at 05:17 No data

  1. Bílovec05:04
  2. Velké Albrechtice05:06
  3. Studénka město05:13
  4. Studénka05:16

Next service: tomorrow 05:04 from Bílovec · Fri 6 Nov

Next departure 05:04 tomorrow · Bílovec
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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 Studénka, 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

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

  • Early 0% · 0
  • On time 100% · 40
  • 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=8
  • 100% W n=8
  • 100% 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 (4 stops).

Last 90 days, 40 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
05:04on time on time
05:06≈ on time ≈ on time
05:13≈ on time ≈ +1 min
05:16on 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
Thu 5 NovStudénka 05:17No data—
Wed 4 NovStudénka 05:17No data—
Tue 3 NovStudénka 05:18No data—
Mon 2 NovStudénka 05:17No data—
Fri 30 OctStudénka 05:17No data—
Thu 29 OctStudénka 05:17No data—
Tue 27 OctStudénka 05:17No data—
Mon 26 OctStudénka 05:17No data—
Fri 23 OctStudénka 05:17No data—
Thu 22 OctStudénka 05:17No data—
Wed 21 OctStudénka 05:17No data—
Tue 20 OctStudénka 05:17No data—
Mon 19 OctStudénka 05:17No data—
Fri 16 OctStudénka 05:17No data—
Thu 15 OctStudénka 05:17No data—
Wed 14 OctStudénka 05:17No data—
Tue 13 OctStudénka 05:17No data—
Mon 12 OctStudénka 05:17No data—
Fri 9 OctStudénka 05:17No data—
Thu 8 OctStudénka 05:17No data—
Wed 7 OctStudénka 05:17No data—
Tue 6 OctStudénka 05:17No data—
Mon 5 Oct— 05:30−1 min—
Fri 2 Oct— 05:29−1 min—
Thu 1 Oct— 05:29−1 min—
Wed 30 Sept— 05:300 min—
Tue 29 Sept— 05:300 min—
Fri 25 Sept— 05:310 min—
Thu 24 Sept— 05:29−1 min—
Wed 23 Sept— 05:300 min—