Sp 7856 7856 Rokycany – Plzeň hl. n.

View line Sp 7856

Rokycany 16:42 → Plzeň hl. n. 16:54 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:42 from Rokycany · Thu 5 Nov

Next departure 16:42 today · Rokycany
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 21 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

  • Thu 24 Sept Max en route +4 min · last fix heading to — +4 min
  • Thu 3 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 15% · 6
  • On time 80% · 32
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 75% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
16:42on time on time
16:45≈ on time ≈ +1 min
16:46≈ on time ≈ +1 min
16:50≈ on time ≈ +1 min
16:54on 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
Wed 4 NovPlzeň hl. n. 16:54No data—
Tue 3 NovPlzeň hl. n. 16:54No data—
Mon 2 NovPlzeň hl. n. 16:54No data—
Fri 30 OctPlzeň hl. n. 16:55No data—
Thu 29 OctPlzeň hl. n. 16:55No data—
Tue 27 OctPlzeň hl. n. 16:55No data—
Mon 26 OctPlzeň hl. n. 16:55No data—
Fri 23 OctPlzeň hl. n. 16:55No data—
Thu 22 OctPlzeň hl. n. 16:55No data—
Wed 21 OctPlzeň hl. n. 16:55No data—
Tue 20 OctPlzeň hl. n. 16:55No data—
Mon 19 OctPlzeň hl. n. 16:55No data—
Fri 16 OctPlzeň hl. n. 16:55No data—
Thu 15 OctPlzeň hl. n. 16:55No data—
Wed 14 OctPlzeň hl. n. 16:55No data—
Tue 13 OctPlzeň hl. n. 16:55No data—
Mon 12 OctPlzeň hl. n. 16:55No data—
Fri 9 OctPlzeň hl. n. 16:55No data—
Thu 8 OctPlzeň hl. n. 16:55No data—
Wed 7 OctPlzeň hl. n. 16:55No data—
Tue 6 OctPlzeň hl. n. 16:55No data—
Mon 5 OctPlzeň hl. n. 16:550 min—
Fri 2 Oct— 17:10+2 min+2 min
Thu 1 Oct— 17:080 min—
Wed 30 Sept— 17:07−2 min—
Tue 29 Sept— 17:06−2 min—
Fri 25 Sept— 17:08−1 min—
Thu 24 Sept— 17:12+4 min+4 min
Wed 23 Sept— 17:08−1 min—
Tue 22 Sept— 17:07−1 min—