Os 12800 12800 Český Těšín → Frýdek-Místek

View line Os 12800

Český Těšín 04:40 → Frýdek-Místek 05:18 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 10 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 20 November No data

Next service: Monday 04:40 from Český Těšín · Mon 23 Nov

Next departure 04:40 Monday · Český Těší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
100%
30/30 runs under 3 min
RT coverage: 30 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 Frýdek-Místek, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
04:40on time +1 min
04:41≈ on time ≈ +1 min
04:45≈ on time ≈ +1 min
04:49≈ on time ≈ +1 min
04:52≈ on time ≈ +1 min
04:56 / 04:58≈ on time ≈ +1 min
05:02≈ on time ≈ on time
05:06≈ on time ≈ on time
05:11≈ on time ≈ on time
05:18on 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 20 NovFrýdek-Místek 05:19No data—
Thu 19 NovFrýdek-Místek 05:19No data—
Wed 18 NovFrýdek-Místek 05:19No data—
Mon 16 NovFrýdek-Místek 05:20No data—
Fri 13 NovFrýdek-Místek 05:19No data—
Thu 12 NovFrýdek-Místek 05:19No data—
Wed 11 NovFrýdek-Místek 05:19No data—
Tue 10 NovFrýdek-Místek 05:19No data—
Mon 9 NovFrýdek-Místek 05:19No data—
Fri 6 NovFrýdek-Místek 05:19No data—
Thu 5 NovFrýdek-Místek 05:19No data—
Wed 4 NovFrýdek-Místek 05:19No data—
Tue 3 NovFrýdek-Místek 05:20No data—
Mon 2 NovFrýdek-Místek 05:19No data—
Fri 30 OctFrýdek-Místek 05:19No data—
Thu 29 OctFrýdek-Místek 05:19No data—
Tue 27 OctFrýdek-Místek 05:19No data—
Mon 26 OctFrýdek-Místek 05:19No data—
Fri 23 OctFrýdek-Místek 05:19No data—
Thu 22 OctFrýdek-Místek 05:19No data—
Wed 21 OctFrýdek-Místek 05:19No data—
Tue 20 OctFrýdek-Místek 05:19No data—
Mon 19 OctFrýdek-Místek 05:19No data—
Fri 16 OctFrýdek-Místek 05:19No data—
Thu 15 OctFrýdek-Místek 05:19No data—
Wed 14 OctFrýdek-Místek 05:19No data—
Tue 13 OctFrýdek-Místek 05:19No data—
Mon 12 OctFrýdek-Místek 05:19No data—
Fri 9 OctFrýdek-Místek 05:19No data—
Thu 8 OctFrýdek-Místek 05:19No data—