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

View line Os 6648

Děčín hl. n. 04:36 → Rumburk 05:53 Daily 1 h 17 min · 18 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Rumburk at 05:54 No data

  1. Děčín hl. n.04:36
  2. Malá Veleň04:45
  3. Markvartice04:56
  4. Horní Kamenice05:08
  5. Kytlice05:17
  6. Rybniště05:39
  7. Rumburk05:53

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

Next departure 04:36 tomorrow · Děčín hl. n.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
96%
54/56 runs under 3 min
RT coverage: 56 full · 0 partial · 34 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+1min
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

  • Sun 27 Sept Max en route +32 min · last fix heading to — +19 min
  • Thu 20 Aug Max en route +22 min · last fix heading to — +13 min

Distribution · 90 days

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

  • Early 39% · 22
  • On time 57% · 32
  • 3–10 min 0% · 0
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • 100% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 56 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
04:36on time +2 min
04:39 / 04:40≈ on time ≈ +2 min
04:42≈ on time ≈ +2 min
04:45≈ on time ≈ +2 min
04:49 / 04:50≈ on time ≈ +2 min
04:52≈ on time ≈ +1 min
04:56≈ on time ≈ +1 min
05:00≈ on time ≈ +1 min
05:05 / 05:06≈ on time ≈ +1 min
05:08≈ on time ≈ +1 min
05:14≈ on time ≈ +1 min
05:17≈ 1 min early ≈ +1 min
05:24 / 05:28≈ 1 min early ≈ +1 min
05:34 / 05:35≈ 1 min early ≈ +1 min
05:39≈ 1 min early ≈ +1 min
05:42≈ 1 min early ≈ +1 min
05:45 / 05:46≈ 1 min early ≈ +1 min
05:531 min early +1 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 NovRumburk 05:54No data—
Sat 7 NovRumburk 05:54No data—
Fri 6 NovRumburk 05:54No data—
Thu 5 NovRumburk 05:54No data—
Wed 4 NovRumburk 05:54No data—
Tue 3 NovRumburk 05:55No data—
Mon 2 NovRumburk 05:54No data—
Sun 1 NovRumburk 05:54No data—
Sat 31 OctRumburk 05:54No data—
Fri 30 OctRumburk 05:54No data—
Thu 29 OctRumburk 05:54No data—
Wed 28 OctRumburk 05:55No data—
Tue 27 OctRumburk 05:54No data—
Mon 26 OctRumburk 05:54No data—
Sun 25 OctRumburk 05:54No data—
Sat 24 OctRumburk 05:54No data—
Fri 23 OctRumburk 05:54No data—
Thu 22 OctRumburk 05:54No data—
Wed 21 OctRumburk 05:54No data—
Tue 20 OctRumburk 05:54No data—
Mon 19 OctRumburk 05:54No data—
Sun 18 OctRumburk 05:54No data—
Sat 17 OctRumburk 05:54No data—
Fri 16 OctRumburk 05:54No data—
Thu 15 OctRumburk 05:54No data—
Wed 14 OctRumburk 05:54No data—
Tue 13 OctRumburk 05:54No data—
Mon 12 OctRumburk 05:54No data—
Sun 11 OctRumburk 05:54No data—
Sat 10 OctRumburk 05:54No data—