Os 7823 7823 Přeštice – Beroun

View line Os 7823

Přeštice 16:09 → Beroun 17:46 Daily 1 h 37 min · 25 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 16:09 from Přeštice · Thu 5 Nov

Next departure 16:09 today · Přeštice
On-time · 30 days
58%
14/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
62%
52/84 runs under 3 min
RT coverage: 84 full · 0 partial · 5 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Beroun, 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 5 Oct Max en route +17 min · last fix heading to Beroun +17 min
  • Tue 29 Sept Max en route +17 min · last fix heading to — +17 min
  • Fri 18 Sept Max en route +13 min · last fix heading to — +12 min
  • Thu 1 Oct Max en route +13 min · last fix heading to — +11 min
  • Sat 3 Oct Max en route +10 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 62% · 52
  • 3–10 min 33% · 28
  • 10–30 min 5% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 62% M n=13
  • 50% T n=12
  • 50% W n=12
  • 70% T n=10
  • 55% F n=11
  • 69% S n=13
  • 77% S n=13

Stops and timetable

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

Last 90 days, 84 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
16:09+1 min +7 min
16:13≈ +1 min ≈ +7 min
16:16 / 16:17≈ +1 min ≈ +6 min
16:21 / 16:22≈ +1 min ≈ +6 min
16:24≈ +1 min ≈ +6 min
16:33≈ +2 min ≈ +6 min
16:36 / 16:37≈ +2 min ≈ +6 min
16:39 / 16:41≈ +2 min ≈ +6 min
16:44≈ +2 min ≈ +6 min
16:49≈ +2 min ≈ +5 min
16:52≈ +2 min ≈ +5 min
16:55 / 16:56≈ +2 min ≈ +5 min
17:00≈ +2 min ≈ +5 min
17:03 / 17:04≈ +2 min ≈ +5 min
17:07≈ +2 min ≈ +5 min
17:09 / 17:10≈ +2 min ≈ +6 min
17:12 / 17:13≈ +2 min ≈ +6 min
17:17≈ +2 min ≈ +6 min
17:22 / 17:26≈ +2 min ≈ +6 min
17:30≈ +1 min ≈ +7 min
17:33≈ +1 min ≈ +7 min
17:36≈ +1 min ≈ +7 min
17:40≈ +1 min ≈ +7 min
17:42≈ +1 min ≈ +7 min
17:46+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
Wed 4 NovBeroun 17:47+2 min+2 min
Tue 3 NovBeroun 17:48+3 min+4 min
Mon 2 NovBeroun 17:48+3 min+3 min
Sun 1 NovBeroun 17:47−1 min+1 min
Sat 31 OctBeroun 17:47−1 min—
Fri 30 OctBeroun 17:54+3 min+11 min
Thu 29 OctBeroun 17:51+1 min+1 min
Wed 28 OctBeroun 17:49+4 min+4 min
Tue 27 OctBeroun 17:51+1 min+2 min
Mon 26 OctBeroun 17:53+3 min+4 min
Sun 25 OctBeroun 17:50+5 min+5 min
Sat 24 OctBeroun 17:470 min—
Fri 23 OctBeroun 17:500 min+3 min
Thu 22 OctBeroun 17:47No data—
Wed 21 OctBeroun 17:47No data—
Tue 20 OctBeroun 17:48No data—
Mon 19 OctBeroun 17:47+5 min+5 min
Sun 18 OctBeroun 18:04+5 min+5 min
Sat 17 OctBeroun 17:47+1 min+1 min
Fri 16 OctBeroun 17:47No data—
Thu 15 OctBeroun 17:47No data—
Wed 14 OctBeroun 17:47+2 min+2 min
Tue 13 OctBeroun 17:470 min+2 min
Mon 12 OctBeroun 17:48−1 min+9 min
Sun 11 OctBeroun 17:470 min—
Sat 10 OctBeroun 17:47+3 min+3 min
Fri 9 OctBeroun 17:47−1 min+7 min
Thu 8 OctBeroun 17:470 min+6 min
Wed 7 OctBeroun 17:51+7 min+7 min
Tue 6 OctBeroun 17:470 min+1 min