Os 8933 8933 Plzeň-Jižní Předměstí – Nepomuk

View line Os 8933

Plzeň-Jižní Předměstí 07:03 → Nepomuk 07:50 Daily 0 h 47 min · 11 stops ARRIVA vlaky s.r.o.

✓ Today’s run finished

Today, last fix heading to Nepomuk at 07:49 No data

  1. Plzeň-Jižní Předměstí07:03
  2. Plzeň-Slovany07:11
  3. Starý Plzenec07:19
  4. Nezvěstice07:27
  5. Blovice07:36
  6. Ždírec u Plzně07:43
  7. Nepomuk07:50

Next service: tomorrow 07:03 from Plzeň-Jižní Předměstí · Sat 21 Nov

Next departure 07:03 tomorrow · Plzeň-Jižní Předměstí
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
48%
21/44 runs under 3 min
RT coverage: 44 full · 0 partial · 46 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+12min
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

  • Wed 2 Sept Max en route +17 min · last fix heading to — +16 min
  • Mon 14 Sept Max en route +17 min · last fix heading to — +14 min
  • Mon 5 Oct Max en route +16 min · last fix heading to — +13 min
  • Wed 9 Sept Max en route +17 min · last fix heading to — +13 min
  • Tue 25 Aug Max en route +16 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 48% · 21
  • 3–10 min 39% · 17
  • 10–30 min 14% · 6
  • 30+ min 0% · 0

On-time by weekday

  • 14% M n=7
  • 17% T n=6
  • 67% W n=6
  • 67% T n=6
  • 17% F n=6
  • 67% S n=6
  • 86% S n=7

Stops and timetable

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

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