804 1058 København Østerport – Göteborg C

View line 804

København Østerport 11:20 → Göteborg C 15:05 Daily 3 h 45 min · 21 stops Skånetrafiken

Running now · updated 13:22

Heading to Göteborg C −6 min

Estimated arrival at Göteborg C 15:05 · 166 km/h

  1. København Østerport11:20
  2. Ørestad11:36
  3. Malmö Triangeln12:06
  4. Landskrona station12:39
  5. Båstad station13:27
  6. Varberg14:25
  7. Göteborg C15:05

Today it is running no worse than usual: typical arrival delay is +2 min; 70% of the last 23 runs arrived on time.

On-time · 30 days
70%
16/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
70%
16/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Göteborg 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

  • Thu 29 Oct Max en route +29 min · last fix heading to — +29 min
  • Wed 11 Nov Max en route +21 min · last fix heading to — +21 min
  • Thu 22 Oct Max en route +31 min · last fix heading to — +12 min
  • Wed 28 Oct Max en route +9 min · last fix heading to — +5 min
  • Thu 12 Nov Max en route +9 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 65% · 15
  • 3–10 min 17% · 4
  • 10–30 min 13% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 33% W n=3
  • 25% T n=4
  • 100% F n=4
  • 100% S n=4
  • 50% S n=2

Stops and timetable

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

Last 90 days, 23 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
11:20on time +9 min
11:22 / 11:23≈ on time ≈ +9 min
11:26 / 11:29≈ on time ≈ +9 min
11:36 / 11:37≈ on time ≈ +9 min
11:39 / 11:40≈ on time ≈ +9 min
11:43 / 11:45≈ on time ≈ +9 min
11:57 / 12:03≈ +1 min ≈ +8 min
12:06≈ +1 min ≈ +8 min
12:10 / 12:12≈ +1 min ≈ +8 min
12:22 / 12:24≈ +2 min ≈ +8 min
12:39≈ +2 min ≈ +7 min
12:54 / 13:01≈ +2 min ≈ +7 min
13:15≈ +2 min ≈ +9 min
13:27≈ +2 min ≈ +10 min
13:33≈ +2 min ≈ +10 min
13:46 / 13:53≈ +2 min ≈ +10 min
14:12≈ +2 min ≈ +10 min
14:25 / 14:26≈ +2 min ≈ +10 min
14:44≈ +2 min ≈ +10 min
14:57≈ +2 min ≈ +10 min
15:05+2 min +10 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
Sat 14 Nov— 13:19−6 min+9 min
Fri 13 Nov— 15:08+1 min+9 min
Thu 12 Nov— 15:09+4 min+9 min
Wed 11 Nov— 15:29+21 min+21 min
Tue 10 Nov— 15:09+3 min+9 min
Mon 9 Nov— 15:09+2 min+20 min
Sat 7 Nov— 15:02+1 min+13 min
Fri 6 Nov— 15:09+1 min+9 min
Thu 5 Nov— 15:140 min+9 min
Wed 4 Nov— 15:13+1 min+20 min
Tue 3 Nov— 15:14+3 min+20 min
Mon 2 Nov— 15:14+2 min+9 min
Sun 1 Nov— 13:24+2 min+2 min
Sat 31 Oct— 13:25+3 min+4 min
Fri 30 Oct— 13:25+2 min+2 min
Thu 29 Oct— 13:47+29 min+29 min
Wed 28 Oct— 15:18+5 min+9 min
Tue 27 Oct— 15:130 min+9 min
Mon 26 Oct— 15:15+3 min+20 min
Sun 25 Oct— 15:17+4 min+19 min
Sat 24 Oct— 15:130 min+16 min
Fri 23 Oct— 15:12−1 min+16 min
Thu 22 Oct— 15:24+12 min+31 min