Os 3476 3476 Opava východ – Krnov

View line Os 3476

Opava východ 18:56 → Krnov 19:33 Mon, Tue, Wed, Thu, Fri 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 18:56 from Opava východ · Thu 5 Nov

Next departure 18:56 today · Opava východ
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
67%
26/39 runs under 3 min
RT coverage: 39 full · 0 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+10min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Krnov, 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 21 Sept Max en route +15 min · last fix heading to — +13 min
  • Tue 29 Sept Max en route +12 min · last fix heading to — +12 min
  • Wed 26 Aug Max en route +14 min · last fix heading to — +10 min
  • Mon 24 Aug Max en route +14 min · last fix heading to — +10 min
  • Thu 20 Aug Max en route +12 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 26
  • 3–10 min 21% · 8
  • 10–30 min 13% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 75% T n=8
  • 63% W n=8
  • 63% T n=8
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
18:56on time on time
19:00 / 19:01≈ on time ≈ +1 min
19:06≈ on time ≈ +3 min
19:12≈ on time ≈ +4 min
19:15 / 19:18≈ +1 min ≈ +5 min
19:23≈ +1 min ≈ +7 min
19:28 / 19:29≈ +1 min ≈ +9 min
19:33+1 min +10 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
Wed 4 NovKrnov 19:34No data—
Tue 3 NovKrnov 19:34No data—
Mon 2 NovKrnov 19:34No data—
Fri 30 OctKrnov 19:34No data—
Thu 29 OctKrnov 19:34No data—
Tue 27 OctKrnov 19:35No data—
Mon 26 OctKrnov 19:34No data—
Fri 23 OctKrnov 19:34No data—
Thu 22 OctKrnov 19:34No data—
Wed 21 OctKrnov 19:34No data—
Tue 20 OctKrnov 19:34No data—
Mon 19 OctKrnov 19:34No data—
Fri 16 OctKrnov 19:34No data—
Thu 15 OctKrnov 19:34No data—
Wed 14 OctKrnov 19:34No data—
Tue 13 OctKrnov 19:34No data—
Mon 12 OctKrnov 19:35No data—
Fri 9 OctKrnov 19:34No data—
Thu 8 OctKrnov 19:34No data—
Wed 7 OctKrnov 19:34No data—
Tue 6 OctKrnov 19:34No data—
Mon 5 OctKrnov 19:34No data—
Fri 2 Oct— 19:53+6 min+7 min
Thu 1 Oct— 19:53+6 min+9 min
Wed 30 Sept— 19:480 min—
Tue 29 Sept— 19:59+12 min+12 min
Fri 25 Sept— 19:480 min+2 min
Thu 24 Sept— 19:52+5 min+8 min
Wed 23 Sept— 19:480 min+6 min
Tue 22 Sept— 19:480 min+4 min