ПВ 50131 Дупница – Петрич

View line ПВ

Дупница 06:25 → Петрич 09:13 Daily 2 h 48 min · 24 stops BDŽ

✓ Today’s run finished

Today it reached Петрич at 09:13 0 min

  1. Дупница06:25
  2. Мурсалево06:44
  3. Благоевград07:11
  4. Стара Кресна07:49
  5. Кресна08:06
  6. Дамяница08:33
  7. Петрич09:13

Next service: tomorrow 06:25 from Дупница · Fri 6 Nov

Next departure 06:25 tomorrow · Дупница
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Петрич +3 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Петрич +3 min
  • Tue 13 Oct Max en route +4 min · last fix heading to Петрич +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
06:25on time on time
06:29 / 06:30≈ on time ≈ on time
06:33 / 06:34≈ on time ≈ on time
06:39 / 06:40≈ on time ≈ on time
06:44 / 06:45≈ on time ≈ on time
06:49 / 06:50≈ on time ≈ on time
06:57 / 06:58≈ on time ≈ +1 min
07:03 / 07:08≈ on time ≈ +1 min
07:11 / 07:12≈ on time ≈ +1 min
07:20 / 07:21≈ on time ≈ +1 min
07:26 / 07:36≈ on time ≈ +1 min
07:40 / 07:41≈ on time ≈ +1 min
07:49 / 07:50≈ on time ≈ +1 min
07:57 / 07:58≈ on time ≈ +1 min
08:02 / 08:03≈ on time ≈ +1 min
08:06 / 08:07≈ on time ≈ +1 min
08:10 / 08:11≈ on time ≈ +1 min
08:16 / 08:17≈ on time ≈ +1 min
08:27 / 08:28≈ on time ≈ +2 min
08:33 / 08:34≈ on time ≈ +2 min
08:40 / 09:00≈ on time ≈ +2 min
09:02 / 09:03≈ on time ≈ +2 min
09:05 / 09:06≈ on time ≈ +2 min
09:13on 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 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
Thu 5 NovПетрич 09:140 min—
Wed 4 NovПетрич 09:17+3 min+4 min
Tue 3 NovПетрич 09:140 min—
Mon 2 NovПетрич 09:140 min+3 min
Sun 1 NovПетрич 09:140 min—
Sat 31 OctПетрич 09:140 min—
Fri 30 OctПетрич 09:140 min—
Thu 29 OctПетрич 09:16+2 min+3 min
Wed 28 OctПетрич 09:17+3 min+4 min
Tue 27 OctПетрич 09:140 min+3 min
Mon 26 OctПетрич 09:140 min—
Sun 25 OctПетрич 09:140 min+3 min
Sat 24 OctПетрич 09:140 min+4 min
Fri 23 OctПетрич 09:150 min+4 min
Thu 22 OctПетрич 09:150 min—
Wed 21 OctПетрич 09:140 min—
Tue 20 OctПетрич 09:140 min—
Mon 19 OctПетрич 09:140 min+3 min
Sun 18 OctПетрич 09:140 min—
Sat 17 OctПетрич 09:14No data—
Fri 16 OctПетрич 09:140 min—
Thu 15 OctПетрич 09:140 min—
Wed 14 OctПетрич 09:140 min+4 min
Tue 13 OctПетрич 09:17+3 min+4 min
Mon 12 OctПетрич 09:140 min—
Sun 11 OctПетрич 09:140 min—
Sat 10 OctПетрич 09:140 min—
Fri 9 OctПетрич 09:140 min—
Thu 8 OctПетрич 09:140 min+5 min
Wed 7 OctПетрич 09:140 min—