Os 7648 7648 Plzeň hl. n. – Plasy

View line Os 7648

Plzeň hl. n. 16:20 → Plasy 16:59 Daily 0 h 39 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Plasy at 16:59 No data

  1. Plzeň hl. n.16:20
  2. Plzeň-Bolevec16:27
  3. Plzeň-Orlík16:30
  4. Horní Bříza zastávka16:39
  5. Horní Bříza16:43
  6. Kaznějov16:52
  7. Plasy16:59

Next service: tomorrow 16:20 from Plzeň hl. n. · Tue 10 Nov

Next departure 16:20 tomorrow · Plzeň hl. n.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
76%
42/55 runs under 3 min
RT coverage: 55 full · 0 partial · 35 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Plasy, 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 25 Sept Max en route +13 min · last fix heading to — +13 min
  • Sat 19 Sept Max en route +9 min · last fix heading to — +8 min
  • Sat 29 Aug Max en route +7 min · last fix heading to — +7 min
  • Mon 17 Aug Max en route +6 min · last fix heading to — +6 min
  • Thu 1 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 42
  • 3–10 min 22% · 12
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 57% T n=7
  • 75% W n=8
  • 88% T n=8
  • 63% F n=8
  • 75% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 55 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
16:20on time +4 min
16:24≈ on time ≈ +4 min
16:27≈ on time ≈ +4 min
16:30≈ +1 min ≈ +4 min
16:33 / 16:34≈ +1 min ≈ +4 min
16:39≈ +1 min ≈ +3 min
16:43≈ +1 min ≈ +4 min
16:47≈ +1 min ≈ +4 min
16:52 / 16:53≈ +1 min ≈ +4 min
16:59+1 min +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
Mon 9 NovPlasy 16:59No data—
Sun 8 NovMladotice 17:09No data—
Sat 7 NovMladotice 17:09No data—
Fri 6 NovPlasy 16:59No data—
Thu 5 NovPlasy 16:59No data—
Wed 4 NovPlasy 16:59No data—
Tue 3 NovPlasy 16:59No data—
Mon 2 NovPlasy 16:59No data—
Sun 1 NovMladotice 17:11No data—
Sat 31 OctMladotice 17:11No data—
Fri 30 OctPlasy 17:00No data—
Thu 29 OctPlasy 17:00No data—
Wed 28 OctMladotice 17:11No data—
Tue 27 OctPlasy 17:00No data—
Mon 26 OctPlasy 17:00No data—
Sun 25 OctMladotice 17:11No data—
Sat 24 OctMladotice 17:11No data—
Fri 23 OctPlasy 17:00No data—
Thu 22 OctPlasy 17:00No data—
Wed 21 OctPlasy 17:00No data—
Tue 20 OctPlasy 17:00No data—
Mon 19 OctPlasy 17:00No data—
Sun 18 OctMladotice 17:11No data—
Sat 17 OctMladotice 17:11No data—
Fri 16 OctPlasy 17:00No data—
Thu 15 OctPlasy 17:00No data—
Wed 14 OctPlasy 17:00No data—
Tue 13 OctPlasy 17:00No data—
Mon 12 OctPlasy 17:00No data—
Sun 11 OctMladotice 17:11No data—