Os 7602 7602 Plzeň hl. n. – Mladotice

View line Os 7602

Plzeň hl. n. 08:20 → Mladotice 09:10 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 13 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Mladotice at 09:09 No data

  1. Plzeň hl. n.08:20
  2. Plzeň-Bolevec08:27
  3. Třemošná u Plzně08:33
  4. Horní Bříza08:43
  5. Kaznějov08:52
  6. Horní Hradiště09:03
  7. Mladotice09:10

Next service: tomorrow 08:20 from Plzeň hl. n. · Wed 11 Nov

Next departure 08:20 tomorrow · Plzeň hl. n.
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
92%
34/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Mladotice, in minutes. One bar per run.

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

Worst days

  • Fri 21 Aug Max en route +13 min · last fix heading to — +13 min
  • Mon 7 Sept Max en route +8 min · last fix heading to — +6 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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:20on time +2 min
08:24≈ on time ≈ +2 min
08:27≈ on time ≈ +2 min
08:30≈ on time ≈ +2 min
08:33 / 08:34≈ on time ≈ +2 min
08:39≈ on time ≈ +2 min
08:43≈ on time ≈ +2 min
08:48≈ on time ≈ +2 min
08:52 / 08:53≈ on time ≈ +2 min
08:59 / 09:00≈ on time ≈ +2 min
09:03≈ on time ≈ +2 min
09:07≈ on time ≈ +2 min
09:10on time +2 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
Tue 10 NovMladotice 09:09No data—
Mon 9 NovMladotice 09:09No data—
Fri 6 NovMladotice 09:09No data—
Thu 5 NovMladotice 09:09No data—
Wed 4 NovMladotice 09:09No data—
Tue 3 NovMladotice 09:09No data—
Mon 2 NovMladotice 09:09No data—
Fri 30 OctMladotice 09:11No data—
Thu 29 OctMladotice 09:11No data—
Tue 27 OctMladotice 09:11No data—
Mon 26 OctMladotice 09:11No data—
Fri 23 OctMladotice 09:11No data—
Thu 22 OctMladotice 09:12No data—
Wed 21 OctMladotice 09:11No data—
Tue 20 OctMladotice 09:11No data—
Mon 19 OctMladotice 09:11No data—
Fri 16 OctMladotice 09:12No data—
Thu 15 OctMladotice 09:12No data—
Wed 14 OctMladotice 09:11No data—
Tue 13 OctMladotice 09:11No data—
Mon 12 OctMladotice 09:11No data—
Fri 9 OctMladotice 09:11No data—
Thu 8 OctMladotice 09:11No data—
Wed 7 OctMladotice 09:11No data—
Tue 6 OctMladotice 09:11No data—
Mon 5 Oct— 09:28+4 min+4 min
Fri 2 Oct— 09:250 min+1 min
Thu 1 Oct— 09:24−1 min+1 min
Wed 30 Sept— 09:23−1 min+3 min
Tue 29 Sept— 09:240 min+1 min