КПВ 50234 Благоевград – Дупница
Alerts for train 50234
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line КПВ.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 21:15 from Благоевград · Thu 5 Nov
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
- Mon 2 Nov Max en route +31 min · last fix heading to Дупница +30 min
- Thu 15 Oct Max en route +21 min · last fix heading to Дупница +21 min
- Wed 21 Oct Max en route +21 min · last fix heading to Дупница +18 min
- Sat 24 Oct Max en route +17 min · last fix heading to Дупница +11 min
- Sun 11 Oct Max en route +12 min · last fix heading to Дупница +10 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 79% · 22
- 3–10 min 4% · 1
- 10–30 min 14% · 4
- 30+ min 4% · 1
On-time by weekday
- 80% M n=5
- 100% T n=4
- 75% W n=4
- 75% T n=4
- 100% F n=4
- 50% S n=4
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 28 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 21:15 | on time | +1 min | |
| 21:19 / 21:20 | ≈ on time | ≈ +2 min | |
| 21:28 / 21:37 | ≈ on time | ≈ +6 min | |
| 21:41 / 21:42 | ≈ on time | ≈ +11 min | |
| 21:47 / 21:48 | ≈ on time | ≈ +13 min | |
| 21:52 / 21:53 | ≈ on time | ≈ +13 min | |
| 21:56 / 21:57 | ≈ on time | ≈ +13 min | |
| 22:02 | on time | +13 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Дупница 22:03 | No data | — |
| Tue 3 Nov | Дупница 22:03 | 0 min | — |
| Mon 2 Nov | Дупница 22:34 | +30 min | +31 min |
| Sun 1 Nov | Дупница 22:03 | 0 min | — |
| Sat 31 Oct | Дупница 22:12 | +9 min | +10 min |
| Fri 30 Oct | Дупница 22:03 | 0 min | — |
| Thu 29 Oct | Дупница 22:03 | 0 min | — |
| Wed 28 Oct | Дупница 22:03 | 0 min | — |
| Tue 27 Oct | Дупница 22:03 | 0 min | — |
| Mon 26 Oct | Дупница 22:03 | 0 min | — |
| Sun 25 Oct | Дупница 22:03 | No data | — |
| Sat 24 Oct | Дупница 22:14 | +11 min | +17 min |
| Fri 23 Oct | Дупница 22:03 | 0 min | — |
| Thu 22 Oct | Дупница 22:03 | 0 min | — |
| Wed 21 Oct | Дупница 22:21 | +18 min | +21 min |
| Tue 20 Oct | Дупница 22:03 | 0 min | — |
| Mon 19 Oct | Дупница 22:03 | 0 min | — |
| Sun 18 Oct | Дупница 22:03 | 0 min | +2 min |
| Sat 17 Oct | Дупница 22:03 | 0 min | +3 min |
| Fri 16 Oct | Дупница 22:03 | 0 min | — |
| Thu 15 Oct | Дупница 22:24 | +21 min | +21 min |
| Wed 14 Oct | Дупница 22:03 | 0 min | — |
| Tue 13 Oct | Дупница 22:04 | 0 min | — |
| Mon 12 Oct | Дупница 22:03 | 0 min | — |
| Sun 11 Oct | Дупница 22:13 | +10 min | +12 min |
| Sat 10 Oct | Дупница 22:03 | 0 min | — |
| Fri 9 Oct | Дупница 22:03 | 0 min | +1 min |
| Thu 8 Oct | Дупница 22:03 | 0 min | +3 min |
| Wed 7 Oct | Дупница 22:05 | +2 min | +5 min |
| Tue 6 Oct | Дупница 22:03 | No data | — |