Os 8951 8951 Pňovany – Nezvěstice

View line Os 8951

Pňovany 06:07 → Nezvěstice 07:00 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 13 stops ARRIVA vlaky s.r.o.

✓ Today’s run finished

Today, last fix heading to Nezvěstice at 06:59 No data

  1. Pňovany06:07
  2. Plešnice06:12
  3. Vochov06:20
  4. Plzeň-Zadní Skvrňany06:26
  5. Plzeň hl. n.06:32
  6. Starý Plzenec06:50
  7. Nezvěstice07:00

Next service: tomorrow 06:07 from Pňovany · Fri 6 Nov

Next departure 06:07 tomorrow · Pňovany
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%
36/39 runs under 3 min
RT coverage: 39 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 Nezvěstice, in minutes. One bar per run.

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

Worst days

  • Tue 22 Sept Max en route +12 min · last fix heading to — +9 min
  • Thu 24 Sept Max en route +6 min · last fix heading to — +5 min
  • Tue 15 Sept Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 36
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Last 90 days, 39 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
06:07on time +3 min
06:10≈ on time ≈ +3 min
06:12≈ on time ≈ +3 min
06:17 / 06:18≈ on time ≈ +2 min
06:20≈ on time ≈ +2 min
06:23 / 06:24≈ on time ≈ +3 min
06:26≈ on time ≈ +3 min
06:28 / 06:29≈ on time ≈ +3 min
06:32 / 06:41≈ on time ≈ +3 min
06:43 / 06:44≈ on time ≈ +2 min
06:50 / 06:52≈ on time ≈ +2 min
06:55 / 06:56≈ on time ≈ +2 min
07: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 NovNezvěstice 06:59No data—
Wed 4 NovNezvěstice 06:59No data—
Tue 3 NovNezvěstice 06:59No data—
Mon 2 NovNezvěstice 06:59No data—
Fri 30 OctNezvěstice 07:01No data—
Thu 29 OctNezvěstice 07:01No data—
Tue 27 OctNezvěstice 07:01No data—
Mon 26 OctNezvěstice 07:01No data—
Fri 23 OctNezvěstice 07:01No data—
Thu 22 OctNezvěstice 07:01No data—
Wed 21 OctNezvěstice 07:01No data—
Tue 20 OctNezvěstice 07:01No data—
Mon 19 OctNezvěstice 07:01No data—
Fri 16 OctNezvěstice 07:01No data—
Thu 15 OctNezvěstice 07:01No data—
Wed 14 OctNezvěstice 07:01No data—
Tue 13 OctNezvěstice 07:01No data—
Mon 12 OctNezvěstice 07:01No data—
Fri 9 OctNezvěstice 07:01No data—
Thu 8 OctNezvěstice 07:01No data—
Wed 7 OctNezvěstice 07:01No data—
Tue 6 OctNezvěstice 07:01No data—
Mon 5 Oct— 07:17+2 min+4 min
Fri 2 Oct— 07:150 min+2 min
Thu 1 Oct— 07:150 min+4 min
Wed 30 Sept— 07:13−1 min+3 min
Tue 29 Sept— 07:140 min+2 min
Fri 25 Sept— 07:14−1 min+4 min
Thu 24 Sept— 07:19+5 min+6 min
Wed 23 Sept— 07:15+1 min+13 min