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

View line БВ

Радомир 18:45 → Кюстендил 20:15 Daily 1 h 30 min · 8 stops BDŽ

✓ Today’s run finished

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

  1. Радомир18:45
  2. Александър Димитров18:57
  3. Калища19:08
  4. Раждавица19:49
  5. Шишковци19:56
  6. Копиловци20:01
  7. Кюстендил20:15

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

Next departure 18:45 tomorrow · Радомир
On-time · 30 days
59%
17/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
57%
17/30 runs under 3 min
RT coverage: 30 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+14min
9 in 10 runs arrive with less than this
30 days: +13 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

  • Mon 2 Nov Max en route +17 min · last fix heading to Кюстендил +16 min
  • Mon 5 Oct Max en route +19 min · last fix heading to Кюстендил +15 min
  • Thu 15 Oct Max en route +15 min · last fix heading to Кюстендил +14 min
  • Tue 13 Oct Max en route +16 min · last fix heading to Кюстендил +14 min
  • Mon 19 Oct Max en route +18 min · last fix heading to Кюстендил +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 57% · 17
  • 3–10 min 23% · 7
  • 10–30 min 20% · 6
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
18:45on time +10 min
18:57 / 18:58≈ on time ≈ +10 min
19:08 / 19:09≈ +1 min ≈ +9 min
19:23 / 19:24≈ +1 min ≈ +8 min
19:49 / 19:50≈ +1 min ≈ +11 min
19:56 / 19:57≈ on time ≈ +12 min
20:01 / 20:02≈ on time ≈ +13 min
20:15on time +14 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Кюстендил 20:140 min—
Wed 4 NovКюстендил 20:18+2 min+7 min
Tue 3 NovКюстендил 20:24+9 min+15 min
Mon 2 NovКюстендил 20:33+16 min+17 min
Sun 1 NovКюстендил 20:140 min—
Sat 31 OctКюстендил 20:17+5 min+6 min
Fri 30 OctКюстендил 20:160 min—
Thu 29 OctКюстендил 20:20+4 min+5 min
Wed 28 OctКюстендил 20:160 min—
Tue 27 OctКюстендил 20:160 min—
Mon 26 OctКюстендил 20:160 min—
Sun 25 OctКюстендил 20:160 min—
Sat 24 OctКюстендил 20:21+5 min+10 min
Fri 23 OctКюстендил 20:160 min—
Thu 22 OctКюстендил 20:160 min—
Wed 21 OctКюстендил 20:170 min—
Tue 20 OctКюстендил 20:160 min—
Mon 19 OctКюстендил 20:30+13 min+18 min
Sun 18 OctКюстендил 20:170 min—
Sat 17 OctКюстендил 20:16No data—
Fri 16 OctКюстендил 20:160 min—
Thu 15 OctКюстендил 20:30+14 min+15 min
Wed 14 OctКюстендил 20:26+10 min+12 min
Tue 13 OctКюстендил 20:30+14 min+16 min
Mon 12 OctКюстендил 20:160 min—
Sun 11 OctКюстендил 20:160 min+9 min
Sat 10 OctКюстендил 20:160 min+4 min
Fri 9 OctКюстендил 20:22+6 min+10 min
Thu 8 OctКюстендил 20:22+5 min+8 min
Wed 7 OctКюстендил 20:21+5 min+11 min