ПВ 20133 Враца – Плевен

View line ПВ

Враца 08:45 → Плевен 10:40 Daily 1 h 55 min · 21 stops BDŽ

It has not run yet today

Last recorded run: Friday 6 November +6 min

Next service: today 08:45 from Враца · Sat 7 Nov

Next departure 08:45 today · Враца
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
84%
26/31 runs under 3 min
RT coverage: 31 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Плевен, in minutes. One bar per run.

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

Worst days

  • Fri 6 Nov Max en route +8 min · last fix heading to Плевен +6 min
  • Thu 8 Oct Max en route +20 min · last fix heading to Плевен +5 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Плевен +4 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Плевен +4 min
  • Sat 24 Oct Max en route +22 min · last fix heading to Плевен +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 26
  • 3–10 min 16% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 100% W n=5
  • 60% T n=5
  • 80% F n=5
  • 75% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 31 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
08:45on time on time
08:52 / 08:53≈ on time ≈ on time
08:56 / 08:57≈ on time ≈ on time
09:01 / 09:03≈ on time ≈ +1 min
09:05 / 09:06≈ on time ≈ +1 min
09:09 / 09:10≈ on time ≈ +1 min
09:12 / 09:13≈ on time ≈ +1 min
09:16 / 09:17≈ on time ≈ +1 min
09:23 / 09:24≈ on time ≈ +1 min
09:27 / 09:28≈ on time ≈ +1 min
09:32 / 09:33≈ on time ≈ +2 min
09:39 / 09:40≈ on time ≈ +2 min
09:45 / 09:46≈ on time ≈ +2 min
09:51 / 09:52≈ on time ≈ +2 min
09:58 / 09:59≈ on time ≈ +3 min
10:06 / 10:07≈ on time ≈ +3 min
10:15 / 10:16≈ on time ≈ +3 min
10:22 / 10:23≈ on time ≈ +3 min
10:30 / 10:31≈ on time ≈ +4 min
10:36 / 10:37≈ on time ≈ +4 min
10:40on 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 5 October 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 NovПлевен 10:47+6 min+8 min
Thu 5 NovПлевен 10:390 min—
Wed 4 NovПлевен 10:420 min—
Tue 3 NovПлевен 10:390 min—
Mon 2 NovПлевен 10:390 min—
Sun 1 NovПлевен 10:410 min—
Sat 31 OctПлевен 10:410 min—
Fri 30 OctПлевен 10:500 min—
Thu 29 OctПлевен 10:500 min+9 min
Wed 28 OctПлевен 10:500 min—
Tue 27 OctПлевен 10:500 min—
Mon 26 OctПлевен 10:500 min—
Sun 25 OctПлевен 10:500 min—
Sat 24 OctПлевен 10:53+3 min+22 min
Fri 23 OctПлевен 10:500 min—
Thu 22 OctПлевен 10:500 min—
Wed 21 OctПлевен 10:500 min—
Tue 20 OctПлевен 10:500 min—
Mon 19 OctПлевен 10:52+2 min+3 min
Sun 18 OctПлевен 10:500 min—
Sat 17 OctПлевен 10:500 min—
Fri 16 OctПлевен 10:52+2 min+2 min
Thu 15 OctПлевен 10:54+4 min+4 min
Wed 14 OctПлевен 10:51+1 min+5 min
Tue 13 OctПлевен 10:54+4 min+5 min
Mon 12 OctПлевен 10:500 min—
Sun 11 OctПлевен 10:500 min—
Sat 10 OctПлевен 10:500 min—
Fri 9 OctПлевен 10:52+2 min+5 min
Thu 8 OctПлевен 10:55+5 min+20 min