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

View line Sp 1344

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

It has not run yet today

Last recorded run: Monday 16 November No data

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

Next departure 12:17 today · Ú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
87%
27/31 runs under 3 min
RT coverage: 31 full · 0 partial · 29 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 Ž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

  • Wed 16 Sept Max en route +19 min · last fix heading to — +16 min
  • Thu 17 Sept Max en route +11 min · last fix heading to — +8 min
  • Tue 15 Sept Max en route +12 min · last fix heading to — +8 min
  • Mon 14 Sept Max en route +9 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 27
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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