Os 6568 6568 Děčín hl. n. – Ústí n.L. západ

View line Os 6568

Děčín hl. n. 22:28 → Ústí n.L. západ 22:58 Tue, Sat, Sun 0 h 30 min · 12 stops RegioJet ÚK a.s.

It does not run today

Last recorded run: Tuesday 17 November No data

Next service: Saturday 22:28 from Děčín hl. n. · Sat 21 Nov

Next departure 22:28 Saturday · Děčín hl. n.
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Ústí n.L. západ, 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 5 Sept Max en route +32 min · last fix heading to — +29 min
  • Sat 22 Aug 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 87% · 13
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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
22:28on time +2 min
22:31≈ on time ≈ +2 min
22:34≈ on time ≈ +2 min
22:36≈ on time ≈ +2 min
22:39 / 22:40≈ on time ≈ +2 min
22:42 / 22:43≈ on time ≈ +2 min
22:44 / 22:45≈ on time ≈ +2 min
22:47≈ on time ≈ +2 min
22:49≈ on time ≈ +3 min
22:51 / 22:52≈ on time ≈ +3 min
22:55 / 22:56≈ on time ≈ +3 min
22:58on time +3 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
Tue 17 NovÚstí n.L. západ 22:59No data—
Sun 15 NovÚstí n.L. západ 23:00No data—
Sat 14 NovÚstí n.L. západ 22:59No data—
Sun 8 NovÚstí n.L. západ 22:59No data—
Sat 7 NovÚstí n.L. západ 22:59No data—
Sun 1 NovÚstí n.L. západ 22:59No data—
Sat 31 OctÚstí n.L. západ 22:59No data—
Wed 28 OctÚstí n.L. západ 22:59No data—
Sun 25 OctÚstí n.L. západ 22:59No data—
Sat 24 OctÚstí n.L. západ 22:59No data—
Sun 18 OctÚstí n.L. západ 22:59No data—
Sat 17 OctÚstí n.L. západ 22:59No data—
Sun 11 OctÚstí n.L. západ 22:59No data—
Sat 10 OctÚstí n.L. západ 22:59No data—
Sun 4 Oct— 23:120 min+2 min
Sat 3 Oct— 23:120 min+2 min
Mon 28 Sept— 23:130 min+1 min
Sun 27 Sept— 23:120 min—
Sat 26 Sept— 23:13+1 min+2 min
Sun 20 Sept— 23:13+1 min+1 min
Sat 19 Sept— 23:13+1 min+1 min
Sun 13 Sept— 23:120 min+1 min
Sat 12 Sept— 23:13+1 min+1 min
Sun 6 Sept— 23:120 min—
Sat 5 Sept— 23:41+29 min+32 min
Sun 30 Aug— 23:120 min—
Sat 29 Aug— 23:120 min+2 min
Sun 23 Aug— 23:120 min+1 min
Sat 22 Aug— 23:17+4 min+4 min