Os 2864 2864 Ostrava-Kunčice – Ostrava-Svinov

View line Os 2864

Ostrava-Kunčice 07:51 → Ostrava-Svinov 08:03 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Ostrava-Svinov at 08:04 No data

  1. Ostrava-Kunčice07:51
  2. Ostrava-Vítkovice07:55
  3. Ostrava-Svinov08:03

Next service: tomorrow 07:51 from Ostrava-Kunčice · Fri 6 Nov

Full trip card
Next departure 07:51 tomorrow · Ostrava-Kunčice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
90%
36/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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 Ostrava-Svinov, in minutes. One bar per run.

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

Worst days

  • Thu 17 Sept Max en route +10 min · last fix heading to — +7 min
  • Tue 15 Sept Max en route +8 min · last fix heading to — +6 min
  • Mon 10 Aug Max en route +5 min · last fix heading to — +5 min
  • Mon 14 Sept Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 36
  • 3–10 min 10% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 88% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
Ostrava-Kunčice
07:51+2 min +5 min
Ostrava-Vítkovice
07:55 / 07:56≈ +1 min ≈ +4 min
Ostrava-Svinov
08:03on 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
Thu 5 NovOstrava-Svinov 08:04No data—
Wed 4 NovOstrava-Svinov 08:04No data—
Tue 3 NovOstrava-Svinov 08:04No data—
Mon 2 NovOstrava-Svinov 08:04No data—
Fri 30 OctOstrava-Svinov 08:04No data—
Thu 29 OctOstrava-Svinov 08:04No data—
Tue 27 OctOstrava-Svinov 08:04No data—
Mon 26 OctOstrava-Svinov 08:04No data—
Fri 23 OctOstrava-Svinov 08:04No data—
Thu 22 OctOstrava-Svinov 08:05No data—
Wed 21 OctOstrava-Svinov 08:04No data—
Tue 20 OctOstrava-Svinov 08:04No data—
Mon 19 OctOstrava-Svinov 08:04No data—
Fri 16 OctOstrava-Svinov 08:04No data—
Thu 15 OctOstrava-Svinov 08:04No data—
Wed 14 OctOstrava-Svinov 08:04No data—
Tue 13 OctOstrava-Svinov 08:04No data—
Mon 12 OctOstrava-Svinov 08:04No data—
Fri 9 OctOstrava-Svinov 08:04No data—
Thu 8 OctOstrava-Svinov 08:04No data—
Wed 7 OctOstrava-Svinov 08:04No data—
Tue 6 OctOstrava-Svinov 08:04No data—
Mon 5 Oct— 08:19+1 min+3 min
Fri 2 Oct— 08:180 min—
Thu 1 Oct— 08:170 min+1 min
Wed 30 Sept— 08:170 min+2 min
Tue 29 Sept— 08:170 min+1 min
Fri 25 Sept— 08:17−1 min+1 min
Thu 24 Sept— 08:190 min—
Wed 23 Sept— 08:17−1 min+2 min