Os 4233 4233 St. Město u U.H. – Otrokovice

View line Os 4233

St. Město u U.H. 05:34 → Otrokovice 05:45 Tue, Sat, Sun 0 h 11 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 8 November No data

Next service: Saturday 05:34 from St. Město u U.H. · Sat 14 Nov

Full trip card
Next departure 05:34 Saturday · St. Město u U.H.
On-time · 30 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
−2min
Median at arrival, 90 days
P90
−1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Otrokovice, 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

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

  • Early 53% · 9
  • On time 47% · 8
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
St. Město u U.H.
05:34on time +1 min
Huštěnovice
05:38≈ 1 min early ≈ +1 min
Spytihněv
05:39≈ 1 min early ≈ on time
Napajedla
05:41≈ 1 min early ≈ on time
Otrokovice
05:452 min early 1 min early

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
Sun 8 NovOtrokovice 05:44No data—
Sat 7 NovOtrokovice 05:44No data—
Sun 1 NovOtrokovice 05:46No data—
Sat 31 OctOtrokovice 05:46No data—
Wed 28 OctOtrokovice 05:47No data—
Sun 25 OctOtrokovice 05:46No data—
Sat 24 OctOtrokovice 05:46No data—
Sun 18 OctOtrokovice 05:46No data—
Sat 17 OctOtrokovice 05:46No data—
Sun 11 OctOtrokovice 05:46No data—
Sat 10 OctOtrokovice 05:46No data—
Sun 4 Oct— 05:58−2 min—
Sat 3 Oct— 05:58−1 min—
Mon 28 Sept— 05:58−2 min—
Sun 27 Sept— 05:58−2 min—
Sat 26 Sept— 05:58−1 min—
Sun 20 Sept— 05:57−2 min—
Sat 19 Sept— 05:59−1 min+2 min
Sun 13 Sept— 05:58−1 min+1 min
Sat 12 Sept— 06:02+2 min+2 min
Sun 6 Sept— 05:57−2 min—
Sat 5 Sept— 05:59−1 min—
Sun 30 Aug— 05:57−2 min—
Sat 29 Aug— 05:58−1 min—
Sun 23 Aug— 05:57−2 min—
Sat 22 Aug— 05:57−2 min—
Sun 16 Aug— 05:57−2 min—
Sat 15 Aug— 05:58−1 min—