Os 16740 16740 Žlutice – Toužim

View line Os 16740

Žlutice 05:03 → Toužim 05:32 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 6 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Toužim at 05:33 No data

  1. Žlutice05:03
  2. Borek u Žlutic05:08
  3. Štědrá05:13
  4. Smilov05:22
  5. Luhov05:26
  6. Toužim05:32

Next service: Monday 05:03 from Žlutice · Mon 9 Nov

Full trip card
Next departure 05:03 Monday · Žlutice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Toužim, 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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
Žlutice
05:03on time on time
Borek u Žlutic
05:08≈ on time ≈ on time
Štědrá
05:13 / 05:14≈ on time ≈ on time
Smilov
05:22≈ on time ≈ on time
Luhov
05:26≈ on time ≈ on time
Toužim
05:32on time on time

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 NovToužim 05:33No data—
Thu 5 NovToužim 05:33No data—
Wed 4 NovToužim 05:33No data—
Tue 3 NovToužim 05:34No data—
Mon 2 NovToužim 05:33No data—
Fri 30 OctToužim 05:33No data—
Thu 29 OctToužim 05:33No data—
Tue 27 OctToužim 05:33No data—
Mon 26 OctToužim 05:33No data—
Fri 23 OctToužim 05:33No data—
Thu 22 OctToužim 05:33No data—
Wed 21 OctToužim 05:33No data—
Tue 20 OctToužim 05:33No data—
Mon 19 OctToužim 05:33No data—
Fri 16 OctToužim 05:33No data—
Thu 15 OctToužim 05:33No data—
Wed 14 OctToužim 05:33No data—
Tue 13 OctToužim 05:33No data—
Mon 12 OctToužim 05:33No data—
Fri 9 OctToužim 05:33No data—
Thu 8 OctToužim 05:33No data—
Wed 7 OctToužim 05:33No data—
Tue 6 OctToužim 05:34No data—
Tue 15 Sept— 05:460 min—
Mon 14 Sept— 05:460 min—
Fri 11 Sept— 05:460 min—
Thu 10 Sept— 05:460 min—
Wed 9 Sept— 05:460 min—
Tue 8 Sept— 05:470 min—
Mon 7 Sept— 05:470 min—