817 1764 Ystad station – Helsingborg C

View line 817

Ystad station 11:46 → Helsingborg C 13:38 Daily 1 h 52 min · 23 stops Skånetrafiken

It has not run yet today

Last recorded run: Tuesday 3 November −1 min

Next service: tomorrow 11:46 from Ystad station · Fri 6 Nov

Next departure 11:46 tomorrow · Ystad station
On-time · 30 days
60%
15/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
71%
42/59 runs under 3 min
RT coverage: 59 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +9 min

Last 30 days

Arrival delay at Helsingborg C, 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 28 Aug Max en route +21 min · last fix heading to — +21 min
  • Tue 13 Oct Max en route +21 min · last fix heading to — +20 min
  • Wed 21 Oct Max en route +15 min · last fix heading to — +15 min
  • Tue 27 Oct Max en route +14 min · last fix heading to — +11 min
  • Tue 25 Aug Max en route +13 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 66% · 39
  • 3–10 min 22% · 13
  • 10–30 min 7% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=10
  • 44% T n=9
  • 50% W n=8
  • 63% T n=8
  • 71% F n=7
  • 89% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 59 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:463 min early on time
11:51≈ 3 min early ≈ on time
11:59≈ 2 min early ≈ on time
12:04≈ 2 min early ≈ on time
12:14≈ 1 min early ≈ +1 min
12:20≈ 1 min early ≈ +1 min
12:29 / 12:30≈ on time ≈ +2 min
12:33≈ on time ≈ +2 min
12:37 / 12:39≈ on time ≈ +2 min
12:44≈ on time ≈ +3 min
12:47≈ on time ≈ +3 min
12:50≈ on time ≈ +3 min
12:53≈ on time ≈ +3 min
12:56 / 12:58≈ on time ≈ +3 min
13:01≈ on time ≈ +4 min
13:06≈ on time ≈ +4 min
13:11≈ on time ≈ +5 min
13:16≈ on time ≈ +5 min
13:20≈ +1 min ≈ +5 min
13:25≈ +1 min ≈ +6 min
13:28≈ +1 min ≈ +6 min
13:33≈ +1 min ≈ +7 min
13:38+1 min +7 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 11 July 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
Tue 3 Nov— 13:47−1 min+1 min
Mon 2 Nov— 13:49+1 min+3 min
Sun 1 Nov— 13:160 min—
Sat 31 Oct— 13:150 min—
Fri 30 Oct— 13:49+2 min+2 min
Thu 29 Oct— 13:46−2 min—
Wed 28 Oct— 13:52+5 min+5 min
Tue 27 Oct— 13:59+11 min+14 min
Mon 26 Oct— 13:52+5 min+5 min
Sun 25 Oct— 13:160 min+1 min
Sat 24 Oct— 13:160 min+1 min
Fri 23 Oct— 13:51+4 min+5 min
Thu 22 Oct— 13:52+5 min+8 min
Wed 21 Oct— 13:59+15 min+15 min
Tue 20 Oct— 13:49+2 min+3 min
Mon 19 Oct— 13:53+5 min+5 min
Sat 17 Oct— 13:15−1 min+3 min
Wed 14 Oct— 13:470 min+8 min
Tue 13 Oct— 14:07+20 min+21 min
Mon 12 Oct— 13:48+1 min+8 min
Sun 11 Oct— 13:160 min+1 min
Sat 10 Oct— 13:21+5 min+7 min
Fri 9 Oct— 13:47−1 min+2 min
Thu 8 Oct— 13:54+7 min+8 min
Wed 7 Oct— 13:47−1 min+2 min
Tue 6 Oct— 13:52+4 min+4 min
Sun 4 Oct— 13:160 min+8 min
Sat 3 Oct— 13:18+2 min+7 min
Fri 2 Oct— 13:47−1 min+3 min
Mon 28 Sept— 13:47−1 min+5 min