Os 13458 13458 Chuchelná – Kravaře ve Slezsku

View line Os 13458

Chuchelná 08:35 → Kravaře ve Slezsku 08:52 Daily 0 h 17 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Kravaře ve Slezsku at 08:53 No data

  1. Chuchelná08:35
  2. Bolatice08:41
  3. Štěpánkovice08:46
  4. Kravaře ve Slezsku08:52

Next service: tomorrow 08:35 from Chuchelná · Sat 7 Nov

Next departure 08:35 tomorrow · Chuchelná
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 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 Kravaře ve Slezsku, 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

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

  • Early 0% · 0
  • On time 100% · 58
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 58 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:35on time on time
08:41≈ on time ≈ on time
08:46 / 08:48≈ on time ≈ on time
08:52on 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 NovKravaře ve Slezsku 08:53No data—
Thu 5 NovKravaře ve Slezsku 08:53No data—
Wed 4 NovKravaře ve Slezsku 08:53No data—
Tue 3 NovKravaře ve Slezsku 08:53No data—
Mon 2 NovKravaře ve Slezsku 08:53No data—
Sun 1 NovKravaře ve Slezsku 08:53No data—
Sat 31 OctKravaře ve Slezsku 08:53No data—
Fri 30 OctKravaře ve Slezsku 08:53No data—
Thu 29 OctKravaře ve Slezsku 08:53No data—
Wed 28 OctKravaře ve Slezsku 08:53No data—
Tue 27 OctKravaře ve Slezsku 08:53No data—
Mon 26 OctKravaře ve Slezsku 08:53No data—
Sun 25 OctKravaře ve Slezsku 08:53No data—
Sat 24 OctKravaře ve Slezsku 08:53No data—
Fri 23 OctKravaře ve Slezsku 08:53No data—
Thu 22 OctKravaře ve Slezsku 08:54No data—
Wed 21 OctKravaře ve Slezsku 08:53No data—
Tue 20 OctKravaře ve Slezsku 08:53No data—
Mon 19 OctKravaře ve Slezsku 08:53No data—
Sun 18 OctKravaře ve Slezsku 08:53No data—
Sat 17 OctKravaře ve Slezsku 08:53No data—
Fri 16 OctKravaře ve Slezsku 08:54No data—
Thu 15 OctKravaře ve Slezsku 08:54No data—
Wed 14 OctKravaře ve Slezsku 08:53No data—
Tue 13 OctKravaře ve Slezsku 08:53No data—
Mon 12 OctKravaře ve Slezsku 08:53No data—
Sun 11 OctKravaře ve Slezsku 08:53No data—
Sat 10 OctKravaře ve Slezsku 08:53No data—
Fri 9 OctKravaře ve Slezsku 08:53No data—
Thu 8 OctKravaře ve Slezsku 08:53No data—