Os 3602 3602 Jeseník – Šumperk

View line Os 3602

Jeseník 05:42 → Šumperk 07:23 Daily 1 h 41 min · 21 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 19 November No data

Next service: today 05:42 from Jeseník · Fri 20 Nov

Next departure 05:42 today · Jeseník
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
82%
36/44 runs under 3 min
RT coverage: 44 full · 0 partial · 45 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Šumperk, in minutes. One bar per run.

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

Worst days

  • Fri 2 Oct Max en route +14 min · last fix heading to — +14 min
  • Wed 23 Sept Max en route +11 min · last fix heading to — +11 min
  • Mon 21 Sept Max en route +7 min · last fix heading to — +7 min
  • Sun 27 Sept Max en route +5 min · last fix heading to — +5 min
  • Fri 25 Sept Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 34% · 15
  • On time 48% · 21
  • 3–10 min 14% · 6
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 83% T n=6
  • 83% W n=6
  • 83% T n=6
  • 67% F n=6
  • 83% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 44 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:42on time +1 min
05:45≈ on time ≈ +1 min
05:48 / 05:49≈ on time ≈ +1 min
05:55 / 05:56≈ on time ≈ +1 min
06:04 / 06:05≈ on time ≈ +1 min
06:08 / 06:09≈ on time ≈ +1 min
06:17 / 06:22≈ on time ≈ +2 min
06:27≈ on time ≈ +2 min
06:31 / 06:32≈ on time ≈ +2 min
06:36≈ 1 min early ≈ +3 min
06:41 / 06:42≈ 1 min early ≈ +3 min
06:45≈ 1 min early ≈ +3 min
06:48≈ 1 min early ≈ +3 min
06:50 / 06:51≈ 1 min early ≈ +3 min
06:54≈ 1 min early ≈ +3 min
06:57≈ 1 min early ≈ +4 min
07:00≈ 1 min early ≈ +4 min
07:03≈ 1 min early ≈ +4 min
07:06≈ 1 min early ≈ +4 min
07:10 / 07:17≈ 1 min early ≈ +4 min
07:231 min early +5 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 19 NovŠumperk 07:24No data—
Wed 18 NovŠumperk 07:24No data—
Tue 17 NovŠumperk 07:24No data—
Mon 16 NovŠumperk 07:24No data—
Sun 15 NovŠumperk 07:24No data—
Sat 14 NovŠumperk 07:24No data—
Fri 13 NovŠumperk 07:24No data—
Thu 12 NovŠumperk 07:24No data—
Wed 11 NovŠumperk 07:24No data—
Tue 10 NovŠumperk 07:24No data—
Mon 9 NovŠumperk 07:24No data—
Sun 8 NovŠumperk 07:24No data—
Sat 7 NovŠumperk 07:24No data—
Fri 6 NovŠumperk 07:24No data—
Thu 5 NovŠumperk 07:24No data—
Wed 4 NovŠumperk 07:24No data—
Tue 3 NovŠumperk 07:24No data—
Mon 2 NovŠumperk 07:24No data—
Sun 1 NovŠumperk 07:24No data—
Sat 31 OctŠumperk 07:24No data—
Fri 30 OctŠumperk 07:24No data—
Thu 29 OctŠumperk 07:24No data—
Wed 28 OctŠumperk 07:24No data—
Tue 27 OctŠumperk 07:24No data—
Mon 26 OctŠumperk 07:24No data—
Sun 25 OctŠumperk 07:24No data—
Sat 24 OctŠumperk 07:24No data—
Fri 23 OctŠumperk 07:24No data—
Thu 22 OctŠumperk 07:24No data—
Wed 21 OctŠumperk 07:24No data—