Os 12860 12860 Hnojník – Frýdek-Místek

View line Os 12860

Hnojník 04:27 → Frýdek-Místek 04:50 Daily 0 h 23 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Frýdek-Místek at 04:49 No data

  1. Hnojník04:27
  2. Horní Tošanovice04:30
  3. Dobratice-Vojkovice04:34
  4. Dobrá u Frýdku-Místku04:39
  5. Frýdek-Místek04:50

Next service: tomorrow 04:27 from Hnojník · Sat 7 Nov

Next departure 04:27 tomorrow · Hnojník
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 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

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 (5 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
04:27on time on time
04:30≈ on time ≈ on time
04:34≈ on time ≈ on time
04:39 / 04:44≈ on time ≈ on time
04:50on 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 NovFrýdek-Místek 04:49No data—
Thu 5 NovFrýdek-Místek 04:49No data—
Wed 4 NovFrýdek-Místek 04:49No data—
Tue 3 NovFrýdek-Místek 04:49No data—
Mon 2 NovFrýdek-Místek 04:49No data—
Sun 1 NovFrýdek-Místek 04:51No data—
Sat 31 OctFrýdek-Místek 04:51No data—
Fri 30 OctFrýdek-Místek 04:51No data—
Thu 29 OctFrýdek-Místek 04:51No data—
Wed 28 OctFrýdek-Místek 04:52No data—
Tue 27 OctFrýdek-Místek 04:51No data—
Mon 26 OctFrýdek-Místek 04:51No data—
Sun 25 OctFrýdek-Místek 04:51No data—
Sat 24 OctFrýdek-Místek 04:51No data—
Fri 23 OctFrýdek-Místek 04:51No data—
Thu 22 OctFrýdek-Místek 04:51No data—
Wed 21 OctFrýdek-Místek 04:51No data—
Tue 20 OctFrýdek-Místek 04:51No data—
Mon 19 OctFrýdek-Místek 04:51No data—
Sun 18 OctFrýdek-Místek 04:51No data—
Sat 17 OctFrýdek-Místek 04:51No data—
Fri 16 OctFrýdek-Místek 04:51No data—
Thu 15 OctFrýdek-Místek 04:51No data—
Wed 14 OctFrýdek-Místek 04:51No data—
Tue 13 OctFrýdek-Místek 04:51No data—
Mon 12 OctFrýdek-Místek 04:51No data—
Sun 11 OctFrýdek-Místek 04:51No data—
Sat 10 OctFrýdek-Místek 04:51No data—
Fri 9 OctFrýdek-Místek 04:51No data—
Thu 8 OctFrýdek-Místek 04:51No data—