Os 8961 8961 Kozolupy – Nepomuk

View line Os 8961

Kozolupy 18:10 → Nepomuk 19:05 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 15 stops ARRIVA vlaky s.r.o.

✓ Today’s run finished

Today, last fix heading to Nepomuk at 19:04 No data

  1. Kozolupy18:10
  2. Plzeň-Křimice18:15
  3. Plzeň hl. n.18:24
  4. Starý Plzenec18:37
  5. Nezvěstice18:45
  6. Ždírec u Plzně18:57
  7. Nepomuk19:05

Next service: Monday 18:10 from Kozolupy · Mon 9 Nov

Next departure 18:10 Monday · Kozolupy
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
79%
31/39 runs under 3 min
RT coverage: 39 full · 0 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Worst days

  • Mon 31 Aug Max en route +18 min · last fix heading to — +13 min
  • Wed 9 Sept Max en route +9 min · last fix heading to — +8 min
  • Fri 25 Sept Max en route +5 min · last fix heading to — +5 min
  • Fri 21 Aug Max en route +8 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +5 min · last fix heading to — +4 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 79% · 31
  • 3–10 min 18% · 7
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=8
  • 50% W n=8
  • 100% T n=8
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
18:10on time on time
18:12≈ on time ≈ on time
18:15 / 18:16≈ on time ≈ on time
18:18≈ on time ≈ +1 min
18:20 / 18:21≈ on time ≈ +1 min
18:24 / 18:28≈ on time ≈ +1 min
18:30 / 18:31≈ on time ≈ +2 min
18:37 / 18:38≈ on time ≈ +2 min
18:41 / 18:42≈ on time ≈ +3 min
18:45 / 18:46≈ on time ≈ +3 min
18:50≈ on time ≈ +3 min
18:53 / 18:54≈ on time ≈ +3 min
18:57 / 18:58≈ on time ≈ +4 min
19:01≈ on time ≈ +4 min
19:05on time +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
Fri 6 NovNepomuk 19:04No data—
Thu 5 NovNepomuk 19:04No data—
Wed 4 NovNepomuk 19:04No data—
Tue 3 NovNepomuk 19:04No data—
Mon 2 NovNepomuk 19:04No data—
Fri 30 OctNepomuk 19:06No data—
Thu 29 OctNepomuk 19:06No data—
Tue 27 OctNepomuk 19:07No data—
Mon 26 OctNepomuk 19:06No data—
Fri 23 OctNepomuk 19:07No data—
Thu 22 OctNepomuk 19:06No data—
Wed 21 OctNepomuk 19:06No data—
Tue 20 OctNepomuk 19:07No data—
Mon 19 OctNepomuk 19:06No data—
Fri 16 OctNepomuk 19:06No data—
Thu 15 OctNepomuk 19:06No data—
Wed 14 OctNepomuk 19:07No data—
Tue 13 OctNepomuk 19:06No data—
Mon 12 OctNepomuk 19:07No data—
Fri 9 OctNepomuk 19:06No data—
Thu 8 OctNepomuk 19:07No data—
Wed 7 OctNepomuk 19:06No data—
Tue 6 OctNepomuk 19:07No data—
Mon 5 OctNepomuk 19:03No data—
Fri 2 Oct— 19:21+2 min+4 min
Thu 1 Oct— 19:190 min+2 min
Wed 30 Sept— 19:23+3 min+3 min
Tue 29 Sept— 19:190 min+2 min
Fri 25 Sept— 19:25+5 min+5 min
Thu 24 Sept— 19:20+1 min+1 min