817 1752 Ystad station – Helsingborg C

View line 817

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

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 05:46 from Ystad station · Tue 10 Nov

Next departure 05:46 today · Ystad station
On-time · 30 days
63%
12/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
67%
36/54 runs under 3 min
RT coverage: 54 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 6 Nov Max en route +26 min · last fix heading to — +25 min
  • Thu 15 Oct Max en route +17 min · last fix heading to — +17 min
  • Tue 15 Sept Max en route +20 min · last fix heading to — +16 min
  • Fri 9 Oct Max en route +10 min · last fix heading to — +10 min
  • Wed 16 Sept Max en route +10 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 63% · 34
  • 3–10 min 28% · 15
  • 10–30 min 6% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 70% M n=10
  • 50% T n=10
  • 75% W n=4
  • 55% T n=11
  • 50% F n=8
  • 100% S n=3
  • 100% S n=8

Stops and timetable

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

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