816 1619 Förslöv station – Helsingborg C

View line 816

Förslöv station 14:10 → Helsingborg C 14:40 Daily 0 h 30 min · 7 stops Skånetrafiken

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: tomorrow 14:10 from Förslöv station · Fri 6 Nov

Next departure 14:10 tomorrow · Förslöv station
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 0 no data
On-time · 90 days
100%
56/56 runs under 3 min
RT coverage: 56 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 2% · 1
  • On time 98% · 55
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=7
  • 100% F n=10
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 56 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
14:103 min early 1 min early
14:15≈ 2 min early ≈ on time
14:19 / 14:20≈ 2 min early ≈ on time
14:27≈ 1 min early ≈ on time
14:31≈ 1 min early ≈ +1 min
14:35≈ on time ≈ +1 min
14:40on time +2 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
Wed 4 Nov— 14:49+2 min+2 min
Mon 2 Nov— 14:48+1 min+1 min
Sun 1 Nov— 14:48−1 min—
Sat 31 Oct— 14:480 min—
Fri 30 Oct— 14:48−1 min—
Wed 28 Oct— 14:480 min—
Tue 27 Oct— 14:480 min—
Sun 25 Oct— 14:480 min—
Sat 24 Oct— 14:480 min—
Fri 23 Oct— 14:48+2 min+2 min
Thu 22 Oct— 14:48+1 min+1 min
Wed 21 Oct— 14:48−1 min—
Tue 20 Oct— 14:49+1 min+1 min
Fri 16 Oct— 14:50+1 min+4 min
Tue 13 Oct— 14:48+1 min+1 min
Sun 11 Oct— 14:480 min—
Sat 10 Oct— 14:48−1 min—
Tue 6 Oct— 14:480 min—
Wed 30 Sept— 14:48−1 min—
Tue 29 Sept— 14:480 min—
Mon 28 Sept— 14:480 min—
Fri 25 Sept— 14:49+2 min+3 min
Thu 24 Sept— 14:480 min—
Tue 22 Sept— 14:480 min—
Sun 20 Sept— 14:47−1 min—
Sat 19 Sept— 14:48−1 min—
Fri 18 Sept— 14:50+2 min+4 min
Thu 17 Sept— 14:48−1 min—
Mon 14 Sept— 14:48+2 min+3 min
Sun 13 Sept— 14:50+2 min+5 min