Os 6662 6662 Děčín hl. n. – Rumburk

View line Os 6662

Děčín hl. n. 17:36 → Rumburk 18:51 Mon, Tue, Wed, Thu, Fri 1 h 15 min · 18 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 17:36 from Děčín hl. n. · Mon 9 Nov

Next departure 17:36 tomorrow · Děčín hl. n.
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
76%
29/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Rumburk, 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 3 Sept Max en route +18 min · last fix heading to — +11 min
  • Thu 27 Aug Max en route +13 min · last fix heading to — +11 min
  • Fri 4 Sept Max en route +11 min · last fix heading to — +9 min
  • Fri 21 Aug Max en route +8 min · last fix heading to — +6 min
  • Fri 2 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 11% · 4
  • On time 66% · 25
  • 3–10 min 18% · 7
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
17:36on time +3 min
17:39 / 17:40≈ on time ≈ +3 min
17:42≈ on time ≈ +3 min
17:45≈ on time ≈ +3 min
17:49 / 17:50≈ on time ≈ +4 min
17:52≈ on time ≈ +4 min
17:56≈ on time ≈ +3 min
18:00≈ on time ≈ +4 min
18:05 / 18:06≈ on time ≈ +4 min
18:08≈ on time ≈ +4 min
18:14≈ on time ≈ +4 min
18:17≈ on time ≈ +4 min
18:24 / 18:28≈ on time ≈ +4 min
18:34≈ on time ≈ +4 min
18:38≈ on time ≈ +4 min
18:41≈ on time ≈ +5 min
18:44≈ on time ≈ +5 min
18:51on time +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
Fri 6 NovRumburk 18:52No data—
Thu 5 NovRumburk 18:52No data—
Wed 4 NovRumburk 18:52No data—
Tue 3 NovRumburk 18:52No data—
Mon 2 NovRumburk 18:52No data—
Fri 30 OctRumburk 18:52No data—
Thu 29 OctRumburk 18:52No data—
Tue 27 OctRumburk 18:53No data—
Mon 26 OctRumburk 18:52No data—
Fri 23 OctRumburk 18:53No data—
Thu 22 OctRumburk 18:52No data—
Wed 21 OctRumburk 18:52No data—
Tue 20 OctRumburk 18:53No data—
Mon 19 OctRumburk 18:52No data—
Fri 16 OctRumburk 18:52No data—
Thu 15 OctRumburk 18:52No data—
Wed 14 OctRumburk 18:52No data—
Tue 13 OctRumburk 18:52No data—
Mon 12 OctRumburk 18:53No data—
Fri 9 OctRumburk 18:52No data—
Thu 8 OctRumburk 18:52No data—
Wed 7 OctRumburk 18:52No data—
Tue 6 OctRumburk 18:52No data—
Mon 5 OctRumburk 18:52No data—
Fri 2 Oct— 19:10+5 min+6 min
Thu 1 Oct— 19:07+1 min+4 min
Wed 30 Sept— 19:05−1 min+3 min
Tue 29 Sept— 19:03−2 min+3 min
Fri 25 Sept— 19:05−1 min—
Thu 24 Sept— 19:04−1 min—