Os 18121 18121 Vimperk – Strakonice

View line Os 18121

Vimperk 03:47 → Strakonice 04:38 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 13 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Strakonice at 04:39 No data

  1. Vimperk03:47
  2. Bohumilice v Čechách zastávka03:57
  3. Lčovice04:06
  4. Nišovice04:15
  5. Hoštice u Volyně04:23
  6. Přední Zborovice04:30
  7. Strakonice04:38

Next service: Monday 03:47 from Vimperk · Mon 9 Nov

Next departure 03:47 Monday · Vimperk
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
93%
37/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Strakonice, 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 17 Aug Max en route +19 min · last fix heading to — +19 min
  • Thu 20 Aug Max en route +5 min · last fix heading to — +4 min
  • Fri 14 Aug Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 37
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 88% 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, 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
03:47on time on time
03:54 / 03:55≈ on time ≈ on time
03:57≈ on time ≈ on time
04:01 / 04:02≈ on time ≈ +1 min
04:06≈ on time ≈ +1 min
04:09≈ on time ≈ +1 min
04:15≈ on time ≈ +1 min
04:19 / 04:20≈ on time ≈ +1 min
04:23≈ on time ≈ +1 min
04:28≈ on time ≈ +2 min
04:30≈ on time ≈ +2 min
04:33≈ on time ≈ +2 min
04:38on time +2 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 NovStrakonice 04:39No data—
Thu 5 NovStrakonice 04:39No data—
Wed 4 NovStrakonice 04:39No data—
Tue 3 NovStrakonice 04:39No data—
Mon 2 NovStrakonice 04:39No data—
Fri 30 OctStrakonice 04:39No data—
Thu 29 OctStrakonice 04:39No data—
Tue 27 OctStrakonice 04:39No data—
Mon 26 OctStrakonice 04:39No data—
Fri 23 OctStrakonice 04:39No data—
Thu 22 OctStrakonice 04:39No data—
Wed 21 OctStrakonice 04:39No data—
Tue 20 OctStrakonice 04:39No data—
Mon 19 OctStrakonice 04:39No data—
Fri 16 OctStrakonice 04:39No data—
Thu 15 OctStrakonice 04:39No data—
Wed 14 OctStrakonice 04:39No data—
Tue 13 OctStrakonice 04:39No data—
Mon 12 OctStrakonice 04:39No data—
Fri 9 OctStrakonice 04:39No data—
Thu 8 OctStrakonice 04:39No data—
Wed 7 OctStrakonice 04:39No data—
Tue 6 OctStrakonice 04:39No data—
Mon 5 Oct— 04:530 min—
Fri 2 Oct— 04:51−1 min—
Thu 1 Oct— 04:51−1 min—
Wed 30 Sept— 04:51−1 min—
Tue 29 Sept— 04:520 min—
Fri 25 Sept— 04:52−1 min—
Thu 24 Sept— 04:51−1 min—