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

View line 804

Göteborg C 08:55 → København Østerport 12:40 Daily 3 h 45 min · 21 stops Skånetrafiken

Running now · updated 12:37

Heading to København Østerport −1 min

Estimated arrival at København Østerport 12:40 · 33 km/h

  1. Göteborg C08:55
  2. Varberg09:34
  3. Båstad station10:32
  4. Landskrona station11:19
  5. Malmö Triangeln11:53
  6. Ørestad12:20
  7. København Østerport12:40

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

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

Last 30 days

Arrival delay at København Østerport, 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 +49 min · last fix heading to — +34 min
  • Sat 24 Oct Max en route +16 min · last fix heading to — +16 min
  • Thu 5 Nov Max en route +11 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 22% · 5
  • On time 65% · 15
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 4% · 1

On-time by weekday

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

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
08:552 min early +7 min
09:02≈ 2 min early ≈ +7 min
09:14≈ 2 min early ≈ +6 min
09:34≈ 2 min early ≈ +6 min
09:47≈ 1 min early ≈ +6 min
10:06 / 10:14≈ 1 min early ≈ +5 min
10:26≈ 1 min early ≈ +5 min
10:32≈ 1 min early ≈ +6 min
10:45≈ 1 min early ≈ +5 min
11:03 / 11:06≈ 1 min early ≈ +5 min
11:19≈ 1 min early ≈ +5 min
11:36 / 11:38≈ 1 min early ≈ +5 min
11:48 / 11:50≈ on time ≈ +6 min
11:53≈ on time ≈ +6 min
11:57 / 11:59≈ on time ≈ +6 min
12:13 / 12:15≈ on time ≈ +6 min
12:17 / 12:18≈ on time ≈ +6 min
12:20 / 12:21≈ on time ≈ +7 min
12:28 / 12:34≈ on time ≈ +7 min
12:36 / 12:37≈ on time ≈ +7 min
12:40on time +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
Sat 14 Nov— 12:34−1 min—
Fri 13 Nov— 11:47−1 min+8 min
Thu 12 Nov— 12:440 min+7 min
Wed 11 Nov— 12:43−1 min+6 min
Tue 10 Nov— 12:19+1 min—
Mon 9 Nov— 12:43−1 min+7 min
Sun 8 Nov— 11:53+1 min—
Sat 7 Nov— 12:44−1 min+6 min
Fri 6 Nov— 12:440 min—
Thu 5 Nov— 12:52+8 min+11 min
Wed 4 Nov— 11:47−2 min—
Tue 3 Nov— 12:490 min+2 min
Mon 2 Nov— 12:490 min—
Sun 1 Nov— 09:44−2 min+9 min
Fri 30 Oct— 09:44+3 min+9 min
Thu 29 Oct— 10:16+34 min+49 min
Wed 28 Oct— 12:49−1 min—
Tue 27 Oct— 12:50−1 min—
Mon 26 Oct— 11:59+1 min+6 min
Sun 25 Oct— 12:500 min+4 min
Sat 24 Oct— 13:05+16 min+16 min
Fri 23 Oct— 12:50+1 min+3 min
Thu 22 Oct— 12:500 min+4 min