КПВ 60213 Радомир – Кюстендил

View line КПВ

Радомир 11:37 → Кюстендил 13:10 Daily 1 h 33 min · 13 stops BDŽ

✓ Today’s run finished

Today it reached Кюстендил at 13:10 0 min

  1. Радомир11:37
  2. Александър Димитров11:49
  3. Егълница11:58
  4. Жабляно12:08
  5. Скакавица12:33
  6. Шишковци12:50
  7. Кюстендил13:10

Next service: tomorrow 11:37 from Радомир · Fri 6 Nov

Next departure 11:37 tomorrow · Радомир
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
86%
25/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
+3min
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

  • Tue 3 Nov Max en route +10 min · last fix heading to Кюстендил +9 min
  • Mon 2 Nov Max en route +8 min · last fix heading to Кюстендил +7 min
  • Fri 9 Oct Max en route +6 min · last fix heading to Кюстендил +4 min
  • Fri 16 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 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
11:37on time on time
11:42 / 11:43≈ on time ≈ on time
11:49 / 11:50≈ on time ≈ on time
11:53 / 11:54≈ on time ≈ +1 min
11:58 / 11:59≈ on time ≈ +1 min
12:01 / 12:02≈ on time ≈ +1 min
12:08 / 12:09≈ on time ≈ +1 min
12:16 / 12:17≈ on time ≈ +1 min
12:33 / 12:34≈ on time ≈ +2 min
12:43 / 12:44≈ on time ≈ +2 min
12:50 / 12:51≈ on time ≈ +3 min
12:55 / 12:56≈ on time ≈ +3 min
13:10on time +3 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Кюстендил 13:090 min—
Wed 4 NovКюстендил 13:120 min—
Tue 3 NovКюстендил 13:19+9 min+10 min
Mon 2 NovКюстендил 13:18+7 min+8 min
Sun 1 NovКюстендил 13:110 min—
Sat 31 OctКюстендил 13:110 min—
Fri 30 OctКюстендил 13:110 min—
Thu 29 OctКюстендил 13:13+2 min+5 min
Wed 28 OctКюстендил 13:110 min—
Tue 27 OctКюстендил 13:110 min—
Mon 26 OctКюстендил 13:110 min—
Sun 25 OctКюстендил 13:110 min—
Sat 24 OctКюстендил 13:110 min—
Fri 23 OctКюстендил 13:110 min—
Thu 22 OctКюстендил 13:110 min—
Wed 21 OctКюстендил 13:110 min—
Tue 20 OctКюстендил 13:110 min—
Mon 19 OctКюстендил 13:110 min—
Sun 18 OctКюстендил 13:110 min—
Sat 17 OctКюстендил 13:11No data—
Fri 16 OctКюстендил 13:14+3 min+4 min
Thu 15 OctКюстендил 13:110 min—
Wed 14 OctКюстендил 13:110 min—
Tue 13 OctКюстендил 13:110 min—
Mon 12 OctКюстендил 13:110 min—
Sun 11 OctКюстендил 13:110 min—
Sat 10 OctКюстендил 13:110 min—
Fri 9 OctКюстендил 13:16+4 min+6 min
Thu 8 OctКюстендил 13:13+2 min+3 min
Wed 7 OctКюстендил 13:120 min—