Sp 2042 2042 Ostrava-Svinov – Ostravice

View line Sp 2042

Ostrava-Svinov 10:06 → Ostravice 10:57 Sat, Sun 0 h 51 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Ostravice at 10:58 No data

  1. Ostrava-Svinov10:06
  2. Ostrava-Kunčice10:19
  3. Paskov10:25
  4. Baška10:37
  5. Frýdlant nad Ostravicí10:44
  6. Frýdlant nad Ostravicí-Nová Dědina10:49
  7. Ostravice10:57

Next service: Saturday 10:06 from Ostrava-Svinov · Sat 14 Nov

Next departure 10:06 Saturday · Ostrava-Svinov
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
53%
9/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+12min
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

  • Sat 5 Sept Max en route +24 min · last fix heading to — +24 min
  • Sun 27 Sept Max en route +14 min · last fix heading to — +14 min
  • Sat 15 Aug Max en route +11 min · last fix heading to — +11 min
  • Sat 22 Aug Max en route +8 min · last fix heading to — +8 min
  • Sun 23 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 53% · 9
  • 3–10 min 29% · 5
  • 10–30 min 18% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 38% S n=8
  • 63% S n=8

Stops and timetable

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

Last 90 days, 17 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
10:06+1 min +5 min
10:13 / 10:14≈ +2 min ≈ +6 min
10:19≈ +1 min ≈ +7 min
10:21≈ +1 min ≈ +7 min
10:25≈ +2 min ≈ +8 min
10:29≈ +2 min ≈ +8 min
10:32 / 10:34≈ +2 min ≈ +9 min
10:37≈ +2 min ≈ +9 min
10:40≈ +2 min ≈ +10 min
10:44 / 10:46≈ +2 min ≈ +10 min
10:47≈ +2 min ≈ +11 min
10:49≈ +2 min ≈ +11 min
10:53 / 10:54≈ +2 min ≈ +12 min
10:57+2 min +12 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 8 NovOstravice 10:58No data—
Sat 7 NovOstravice 10:58No data—
Sun 1 NovOstravice 10:58No data—
Sat 31 OctOstravice 10:58No data—
Wed 28 OctOstravice 10:58No data—
Sun 25 OctOstravice 10:58No data—
Sat 24 OctOstravice 10:58No data—
Sun 18 OctOstravice 10:58No data—
Sat 17 OctOstravice 10:58No data—
Sun 11 OctOstravice 10:58No data—
Sat 10 OctOstravice 10:58No data—
Sun 4 Oct— 11:110 min—
Sat 3 Oct— 11:13+1 min+4 min
Mon 28 Sept— 11:120 min+2 min
Sun 27 Sept— 11:05+14 min+14 min
Sat 26 Sept— 11:16+4 min+6 min
Sun 20 Sept— 11:110 min+1 min
Sat 19 Sept— 11:130 min+5 min
Sun 13 Sept— 11:120 min+1 min
Sat 12 Sept— 11:120 min+2 min
Sun 6 Sept— 11:120 min+1 min
Sat 5 Sept— 11:36+24 min+24 min
Sun 30 Aug— 11:23+2 min+5 min
Sat 29 Aug— 11:25+4 min+4 min
Sun 23 Aug— 11:25+5 min+5 min
Sat 22 Aug— 11:28+8 min+8 min
Sun 16 Aug— 11:25+5 min+5 min
Sat 15 Aug— 11:31+11 min+11 min