Os 3768 3768 Zábřeh na Moravě – Rudoltice v Čechách

View line Os 3768

Zábřeh na Moravě 05:02 → Rudoltice v Čechách 05:29 Tue, Sat, Sun 0 h 27 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Rudoltice v Čechách at 05:29 No data

  1. Zábřeh na Moravě05:02
  2. Hoštejn05:10
  3. Hoštejn05:14
  4. Krasíkov05:19
  5. Krasíkov05:21
  6. Luková u Rudoltic v Čechách05:26
  7. Rudoltice v Čechách05:29

Next service: Tuesday 05:02 from Zábřeh na Moravě · Tue 17 Nov

Next departure 05:02 Tuesday · Zábřeh na Moravě
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
40%
6/15 runs under 3 min
RT coverage: 15 full · 0 partial · 13 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+7min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Rudoltice v Čechách, 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 29 Aug Max en route +7 min · last fix heading to — +7 min
  • Sat 22 Aug Max en route +7 min · last fix heading to — +7 min
  • Sat 12 Sept Max en route +10 min · last fix heading to — +6 min
  • Sat 3 Oct Max en route +6 min · last fix heading to — +5 min
  • Sat 26 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 40% · 6
  • 3–10 min 60% · 9
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
05:02on time +3 min
05:05≈ on time ≈ +3 min
05:10 / 05:13≈ +1 min ≈ +3 min
05:14≈ +2 min ≈ +3 min
05:17≈ +2 min ≈ +4 min
05:19 / 05:20≈ +3 min ≈ +4 min
05:21≈ +3 min ≈ +5 min
05:23≈ +3 min ≈ +5 min
05:26≈ +4 min ≈ +6 min
05:29+4 min +7 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 15 NovRudoltice v Čechách 05:29No data—
Sat 14 NovRudoltice v Čechách 05:29No data—
Sun 8 NovRudoltice v Čechách 05:29No data—
Sat 7 NovRudoltice v Čechách 05:29No data—
Sun 1 NovRudoltice v Čechách 05:31No data—
Sat 31 OctRudoltice v Čechách 05:31No data—
Wed 28 OctRudoltice v Čechách 05:31No data—
Sun 25 OctRudoltice v Čechách 05:31No data—
Sat 24 OctRudoltice v Čechách 05:31No data—
Sun 18 OctRudoltice v Čechách 05:31No data—
Sat 17 OctRudoltice v Čechách 05:31No data—
Sun 11 OctRudoltice v Čechách 05:31No data—
Sat 10 OctRudoltice v Čechách 05:31No data—
Sun 4 Oct— 05:440 min—
Sat 3 Oct— 05:49+5 min+6 min
Mon 28 Sept— 05:47+2 min+2 min
Sun 27 Sept— 05:46+1 min+1 min
Sat 26 Sept— 05:48+4 min+4 min
Sun 20 Sept— 05:46+3 min+3 min
Sat 19 Sept— 05:49+4 min+4 min
Sun 13 Sept— 05:45+2 min+3 min
Sat 12 Sept— 05:51+6 min+10 min
Sun 6 Sept— 05:440 min—
Sat 5 Sept— 05:49+4 min+4 min
Sun 30 Aug— 05:430 min+3 min
Sat 29 Aug— 05:52+7 min+7 min
Sun 23 Aug— 05:47+4 min+4 min
Sat 22 Aug— 05:50+7 min+7 min