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

View line 804

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

✓ Today’s run finished

Today, last fix heading to — at 10:44 +1 min

  1. Göteborg C06:55
  2. Varberg07:34
  3. Båstad station08:32
  4. Landskrona station09:19
  5. Malmö Triangeln09:53
  6. Ørestad10:20
  7. København Østerport10:40

Next service: tomorrow 06:55 from Göteborg C · Sun 15 Nov

Next departure 06:55 tomorrow · Göteborg C
On-time · 30 days
65%
15/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
65%
15/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
+9min
9 in 10 runs arrive with less than this
30 days: +9 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 +41 min · last fix heading to — +41 min
  • Mon 26 Oct Max en route +34 min · last fix heading to — +34 min
  • Thu 5 Nov Max en route +10 min · last fix heading to — +10 min
  • Sat 24 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 30 Oct Max en route +14 min · last fix heading to — +7 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 61% · 14
  • 3–10 min 26% · 6
  • 10–30 min 0% · 0
  • 30+ min 9% · 2

On-time by weekday

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