805 1110 København Østerport – Helsingborg C

View line 805

København Østerport 17:50 → Helsingborg C 19:24 Daily 1 h 34 min · 13 stops Skånetrafiken

Running now · updated 19:47

Heading to Helsingborg C +23 min

Estimated arrival at Helsingborg C 19:47 19:24 · 44 km/h

  1. København Østerport17:50
  2. København H17:56
  3. Tårnby18:09
  4. Malmö Hyllie18:27
  5. Malmö C18:40
  6. Landskrona station19:09
  7. Helsingborg C19:24

Today it is running worse than usual: typical arrival delay is 0 min; 72% of the last 29 runs arrived on time.

On-time · 30 days
72%
21/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
72%
21/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+27min
9 in 10 runs arrive with less than this
30 days: +27 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

  • Wed 18 Nov Max en route +61 min · last fix heading to — +53 min
  • Mon 16 Nov Max en route +57 min · last fix heading to — +48 min
  • Thu 19 Nov Max en route +33 min · last fix heading to — +33 min
  • Tue 17 Nov Max en route +35 min · last fix heading to — +25 min
  • Sat 31 Oct Max en route +15 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 31% · 9
  • On time 41% · 12
  • 3–10 min 14% · 4
  • 10–30 min 3% · 1
  • 30+ min 10% · 3

On-time by weekday

  • 50% M n=4
  • 75% T n=4
  • 50% W n=4
  • 80% T n=5
  • 100% F n=4
  • 75% S n=4
  • 75% 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 10Today
17:501 min early on time
17:52 / 17:53≈ on time ≈ on time
17:56 / 17:59≈ on time ≈ +1 min
18:06 / 18:07≈ on time ≈ +4 min
18:09 / 18:10≈ on time ≈ +5 min
18:13 / 18:15≈ on time ≈ +6 min
18:27 / 18:33≈ on time ≈ +10 min
18:36≈ on time ≈ +13 min
18:40 / 18:42≈ on time ≈ +14 min
18:52 / 18:54≈ on time ≈ +18 min
19:09≈ on time ≈ +23 min
19:19≈ on time ≈ +25 min
19:24on time +27 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
Thu 19 Nov— 19:44+33 min+33 min
Wed 18 Nov— 20:22+53 min+61 min
Tue 17 Nov— 19:54+25 min+35 min
Mon 16 Nov— 20:14+48 min+57 min
Sun 15 Nov— 19:290 min+13 min
Sat 14 Nov— 19:27−1 min+3 min
Fri 13 Nov— 19:29+2 min+11 min
Thu 12 Nov— 19:29+1 min+11 min
Wed 11 Nov— 19:38+4 min+13 min
Tue 10 Nov— 19:380 min+4 min
Mon 9 Nov— 19:29−2 min+3 min
Sun 8 Nov— 19:29+2 min+7 min
Sat 7 Nov— 18:14−2 min—
Fri 6 Nov— 19:290 min+3 min
Thu 5 Nov— 19:34−1 min+3 min
Wed 4 Nov— 19:340 min+11 min
Tue 3 Nov— 19:34+2 min+16 min
Mon 2 Nov— 19:34+3 min+4 min
Sun 1 Nov— 19:32−2 min+2 min
Sat 31 Oct— 19:40+6 min+15 min
Fri 30 Oct— 19:32−2 min+3 min
Thu 29 Oct— 19:33−1 min+13 min
Wed 28 Oct— 19:36−1 min+7 min
Tue 27 Oct— 19:36+2 min+16 min
Mon 26 Oct— 19:370 min+7 min
Sun 25 Oct— 19:38+4 min+4 min
Sat 24 Oct— 19:36−2 min+2 min
Fri 23 Oct— 19:340 min+3 min
Thu 22 Oct— 19:35+1 min+13 min