Os 12924 12924 Frýdlant nad Ostravicí – Ostravice

View line Os 12924

Frýdlant nad Ostravicí 14:48 → Ostravice 14:57 Sat, Sun 0 h 09 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: Saturday 14:48 from Frýdlant nad Ostravicí · Sat 7 Nov

Next departure 14:48 Saturday · Frýdlant nad Ostravicí
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
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Ostravice, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 28 Sept Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
14:48on time +2 min
14:49≈ on time ≈ +2 min
14:51≈ on time ≈ +2 min
14:54≈ on time ≈ +2 min
14:57on time +2 min

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 1 NovOstravice 14:58No data—
Sat 31 OctOstravice 14:58No data—
Wed 28 OctOstravice 14:58No data—
Sun 25 OctOstravice 14:58No data—
Sat 24 OctOstravice 14:58No data—
Sun 18 OctOstravice 14:58No data—
Sat 17 OctOstravice 14:58No data—
Sun 11 OctOstravice 14:58No data—
Sat 10 OctOstravice 14:58No data—
Sun 4 Oct— 15:14+2 min+2 min
Sat 3 Oct— 15:120 min—
Mon 28 Sept— 15:16+5 min+5 min
Sun 27 Sept— 15:120 min—
Sat 26 Sept— 15:120 min—
Sun 20 Sept— 15:12+1 min+1 min
Sat 19 Sept— 15:14+2 min+2 min
Sun 13 Sept— 15:120 min—
Sat 12 Sept— 15:120 min—
Sun 6 Sept— 15:110 min—
Sat 5 Sept— 15:120 min—
Sun 9 Aug— 15:120 min—
Sat 8 Aug— 15:120 min—