Os 8963 8963 Kozolupy – Nepomuk

View line Os 8963

Kozolupy 20:50 → Nepomuk 21:50 Daily 1 h 00 min · 15 stops ARRIVA vlaky s.r.o.

It has not run yet today

Last recorded run: Thursday 19 November No data

Next service: today 20:50 from Kozolupy · Fri 20 Nov

Next departure 20:50 today · Kozolupy
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
53%
23/43 runs under 3 min
RT coverage: 43 full · 0 partial · 46 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+7min
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

  • Sun 4 Oct Max en route +21 min · last fix heading to — +13 min
  • Wed 26 Aug Max en route +15 min · last fix heading to — +11 min
  • Fri 18 Sept Max en route +10 min · last fix heading to — +8 min
  • Wed 9 Sept Max en route +8 min · last fix heading to — +7 min
  • Sun 23 Aug Max en route +10 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 53% · 23
  • 3–10 min 42% · 18
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 83% T n=6
  • 50% W n=6
  • 67% T n=6
  • 50% F n=6
  • 33% S n=6
  • 29% S n=7

Stops and timetable

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

Last 90 days, 43 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
20:50on time +1 min
20:52≈ on time ≈ +1 min
20:55 / 20:56≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:00 / 21:01≈ +1 min ≈ +2 min
21:04 / 21:09≈ +1 min ≈ +2 min
21:11 / 21:12≈ +1 min ≈ +3 min
21:19 / 21:20≈ +1 min ≈ +4 min
21:23 / 21:24≈ +1 min ≈ +4 min
21:27 / 21:29≈ +1 min ≈ +5 min
21:32≈ +1 min ≈ +5 min
21:36 / 21:39≈ +1 min ≈ +5 min
21:43≈ +1 min ≈ +6 min
21:46≈ +1 min ≈ +6 min
21:50+1 min +7 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 19 NovNepomuk 21:49No data—
Wed 18 NovNepomuk 21:49No data—
Tue 17 NovNepomuk 21:49No data—
Mon 16 NovNepomuk 21:49No data—
Sun 15 NovNepomuk 21:49No data—
Sat 14 NovNepomuk 21:49No data—
Fri 13 NovNepomuk 21:49No data—
Thu 12 NovNepomuk 21:49No data—
Wed 11 NovNepomuk 21:49No data—
Tue 10 NovNepomuk 21:50No data—
Mon 9 NovNepomuk 21:49No data—
Sun 8 NovNepomuk 21:49No data—
Sat 7 NovNepomuk 21:49No data—
Fri 6 NovNepomuk 21:49No data—
Thu 5 NovNepomuk 21:49No data—
Wed 4 NovNepomuk 21:49No data—
Tue 3 NovNepomuk 21:49No data—
Mon 2 NovNepomuk 21:49No data—
Sun 1 NovNepomuk 21:49No data—
Sat 31 OctNepomuk 21:51No data—
Fri 30 OctNepomuk 21:51No data—
Thu 29 OctNepomuk 21:51No data—
Wed 28 OctNepomuk 21:51No data—
Tue 27 OctNepomuk 21:52No data—
Mon 26 OctNepomuk 21:51No data—
Sun 25 OctNepomuk 21:51No data—
Sat 24 OctNepomuk 21:51No data—
Fri 23 OctNepomuk 21:51No data—
Thu 22 OctNepomuk 21:51No data—
Wed 21 OctNepomuk 21:51No data—