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

View line Sp 1340

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 08:17 from Ústí n. L. hl. n. · Mon 9 Nov

Next departure 08:17 tomorrow · Ústí n. L. 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
85%
33/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+8min
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

Worst days

  • Tue 22 Sept Max en route +24 min · last fix heading to — +15 min
  • Mon 14 Sept Max en route +13 min · last fix heading to — +10 min
  • Wed 9 Sept Max en route +13 min · last fix heading to — +10 min
  • Tue 15 Sept Max en route +12 min · last fix heading to — +9 min
  • Thu 17 Sept Max en route +13 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 33
  • 3–10 min 8% · 3
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 75% T n=8
  • 75% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

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