Os 12939 12939 Ostravice – Frýdek-Místek

View line Os 12939

Ostravice 22:34 → Frýdek-Místek 23:11 Daily 0 h 37 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 22:34 from Ostravice · Thu 5 Nov

Next departure 22:34 today · Ostravice
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 31 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

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

  • Early 5% · 2
  • On time 95% · 35
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 37 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
22:34on time on time
22:37≈ on time ≈ on time
22:40≈ on time ≈ on time
22:43≈ on time ≈ on time
22:45 / 22:55≈ on time ≈ on time
22:59≈ on time ≈ on time
23:03 / 23:07≈ on time ≈ on time
23:11on 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
Wed 4 NovFrýdek-Místek 23:12No data—
Tue 3 NovFrýdek-Místek 23:12No data—
Mon 2 NovFrýdek-Místek 23:12No data—
Sun 1 NovFrýdek-Místek 23:12No data—
Sat 31 OctFrýdek-Místek 23:12No data—
Fri 30 OctFrýdek-Místek 23:12No data—
Thu 29 OctFrýdek-Místek 23:12No data—
Wed 28 OctFrýdek-Místek 23:12No data—
Tue 27 OctFrýdek-Místek 23:13No data—
Mon 26 OctFrýdek-Místek 23:12No data—
Sun 25 OctFrýdek-Místek 23:12No data—
Sat 24 OctFrýdek-Místek 23:12No data—
Fri 23 OctFrýdek-Místek 23:12No data—
Thu 22 OctFrýdek-Místek 23:12No data—
Wed 21 OctFrýdek-Místek 23:12No data—
Tue 20 OctFrýdek-Místek 23:12No data—
Mon 19 OctFrýdek-Místek 23:13No data—
Sun 18 OctFrýdek-Místek 23:12No data—
Sat 17 OctFrýdek-Místek 23:12No data—
Fri 16 OctFrýdek-Místek 23:12No data—
Thu 15 OctFrýdek-Místek 23:12No data—
Wed 14 OctFrýdek-Místek 23:12No data—
Tue 13 OctFrýdek-Místek 23:12No data—
Mon 12 OctFrýdek-Místek 23:12No data—
Sun 11 OctFrýdek-Místek 23:12No data—
Sat 10 OctFrýdek-Místek 23:12No data—
Fri 9 OctFrýdek-Místek 23:12No data—
Thu 8 OctFrýdek-Místek 23:13No data—
Wed 7 OctFrýdek-Místek 23:12No data—
Tue 6 OctFrýdek-Místek 23:12No data—