Os 7661 7661 Plasy – Plzeň hl. n.

View line Os 7661

Plasy 04:21 → Plzeň hl. n. 05:00 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Plzeň hl. n. at 04:59 No data

  1. Plasy04:21
  2. Obora u Kaznějova04:33
  3. Horní Bříza04:37
  4. Třemošná u Plzně04:46
  5. Plzeň-Orlík04:50
  6. Plzeň-Bílá Hora04:56
  7. Plzeň hl. n.05:00

Next service: tomorrow 04:21 from Plasy · Fri 6 Nov

Next departure 04:21 tomorrow · Plasy
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
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Plzeň hl. n., 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 +4 min · last fix heading to — +3 min
  • Mon 10 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=8
  • 100% W n=8
  • 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 (10 stops).

Last 90 days, 40 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
04:21on time +1 min
04:27 / 04:28≈ on time ≈ +1 min
04:33≈ on time ≈ +1 min
04:37≈ on time ≈ +1 min
04:40 / 04:41≈ on time ≈ +1 min
04:46 / 04:47≈ on time ≈ +1 min
04:50≈ on time ≈ +1 min
04:53≈ on time ≈ +1 min
04:56≈ on time ≈ +1 min
05:00on time +1 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
Thu 5 NovPlzeň hl. n. 04:59No data—
Wed 4 NovPlzeň hl. n. 04:59No data—
Tue 3 NovPlzeň hl. n. 04:59No data—
Mon 2 NovPlzeň hl. n. 04:59No data—
Fri 30 OctPlzeň hl. n. 05:01No data—
Thu 29 OctPlzeň hl. n. 05:01No data—
Tue 27 OctPlzeň hl. n. 05:01No data—
Mon 26 OctPlzeň hl. n. 05:01No data—
Fri 23 OctPlzeň hl. n. 05:01No data—
Thu 22 OctPlzeň hl. n. 05:01No data—
Wed 21 OctPlzeň hl. n. 05:01No data—
Tue 20 OctPlzeň hl. n. 05:01No data—
Mon 19 OctPlzeň hl. n. 05:01No data—
Fri 16 OctPlzeň hl. n. 05:01No data—
Thu 15 OctPlzeň hl. n. 05:01No data—
Wed 14 OctPlzeň hl. n. 05:01No data—
Tue 13 OctPlzeň hl. n. 05:01No data—
Mon 12 OctPlzeň hl. n. 05:01No data—
Fri 9 OctPlzeň hl. n. 05:01No data—
Thu 8 OctPlzeň hl. n. 05:01No data—
Wed 7 OctPlzeň hl. n. 05:01No data—
Tue 6 OctPlzeň hl. n. 05:01No data—
Mon 5 Oct— 05:140 min+1 min
Fri 2 Oct— 05:140 min—
Thu 1 Oct— 05:140 min+2 min
Wed 30 Sept— 05:13−1 min—
Tue 29 Sept— 05:13−1 min—
Fri 25 Sept— 05:160 min+1 min
Thu 24 Sept— 05:140 min—
Wed 23 Sept— 05:140 min+1 min