Sp 1350 1350 Ústí n. L. hl. n. – Žatec

View line Sp 1350

Ústí n. L. hl. n. 18:17 → Žatec 19:51 Mon, Tue, Wed, Thu, Fri, Sun 1 h 34 min · 29 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Wednesday 18 November No data

Next service: today 18:17 from Ústí n. L. hl. n. · Thu 19 Nov

Next departure 18:17 today · Ústí n. L. hl. n.
On-time · 30 days
—
Too little data (0/25 runs with data)
RT coverage: 0 full · 0 partial · 25 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Žatec, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 36 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
18:17on time +4 min
18:24≈ on time ≈ +4 min
18:26≈ on time ≈ +4 min
18:27≈ on time ≈ +4 min
18:30≈ on time ≈ +3 min
18:32≈ on time ≈ +3 min
18:34 / 18:37≈ on time ≈ +3 min
18:40≈ on time ≈ +3 min
18:43≈ on time ≈ +3 min
18:46≈ on time ≈ +3 min
18:50≈ on time ≈ +3 min
18:52≈ on time ≈ +3 min
18:55 / 18:57≈ on time ≈ +2 min
19:00≈ on time ≈ +2 min
19:02≈ on time ≈ +2 min
19:04≈ on time ≈ +2 min
19:05≈ on time ≈ +2 min
19:08≈ on time ≈ +2 min
19:12≈ on time ≈ +2 min
19:15≈ on time ≈ +1 min
19:19 / 19:20≈ on time ≈ +1 min
19:22≈ on time ≈ +1 min
19:24≈ on time ≈ +1 min
19:30≈ on time ≈ +1 min
19:34 / 19:35≈ on time ≈ +1 min
19:41 / 19:43≈ on time ≈ +1 min
19:45≈ on time ≈ +1 min
19:47≈ on time ≈ +1 min
19:51on time +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
Wed 18 NovŽatec 19:52No data—
Tue 17 NovŽatec 19:52No data—
Mon 16 NovŽatec 19:52No data—
Sun 15 NovŽatec 19:52No data—
Fri 13 NovŽatec 19:52No data—
Thu 12 NovŽatec 19:52No data—
Wed 11 NovŽatec 19:52No data—
Tue 10 NovŽatec 19:52No data—
Mon 9 NovŽatec 19:52No data—
Sun 8 NovŽatec 19:52No data—
Fri 6 NovŽatec 19:52No data—
Thu 5 NovŽatec 19:52No data—
Wed 4 NovŽatec 19:52No data—
Tue 3 NovŽatec 19:52No data—
Mon 2 NovŽatec 19:52No data—
Sun 1 NovŽatec 19:52No data—
Fri 30 OctŽatec 19:52No data—
Thu 29 OctŽatec 19:52No data—
Wed 28 OctŽatec 19:52No data—
Tue 27 OctŽatec 19:53No data—
Mon 26 OctŽatec 19:52No data—
Sun 25 OctŽatec 19:52No data—
Fri 23 OctŽatec 19:52No data—
Thu 22 OctŽatec 19:52No data—
Wed 21 OctŽatec 19:52No data—
Tue 20 OctŽatec 19:52No data—
Mon 19 OctŽatec 19:52No data—
Sun 18 OctŽatec 19:52No data—
Fri 16 OctŽatec 19:52No data—
Thu 15 OctŽatec 19:52No data—