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

View line Sp 1346

Ústí n. L. hl. n. 14:17 → Žatec 15: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 14:17 from Ústí n. L. hl. n. · Mon 9 Nov

Next departure 14: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
+4min
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

  • Thu 17 Sept Max en route +15 min · last fix heading to — +12 min
  • Wed 16 Sept Max en route +13 min · last fix heading to — +10 min
  • Mon 14 Sept Max en route +12 min · last fix heading to — +9 min
  • Fri 28 Aug Max en route +5 min · last fix heading to — +5 min
  • Fri 18 Sept Max en route +7 min · last fix heading to — +4 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 10% · 4
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

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