803 1057 Växjö – København Østerport

View line 803

Växjö 09:05 → København Østerport 11:55 Daily 2 h 50 min · 18 stops Skånetrafiken

✓ Today’s run finished

Today, last fix heading to — at 12:14 +17 min

  1. Växjö09:05
  2. Osby station09:54
  3. Eslöv station10:39
  4. Malmö C11:03
  5. Malmö Hyllie11:12
  6. Ørestad11:35
  7. København Østerport11:55

Next service: tomorrow 09:05 from Växjö · Sun 15 Nov

Next departure 09:05 tomorrow · Växjö
On-time · 30 days
71%
17/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
71%
17/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +13 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

  • Sat 31 Oct Max en route +23 min · last fix heading to — +22 min
  • Sat 14 Nov Max en route +17 min · last fix heading to — +17 min
  • Tue 27 Oct Max en route +49 min · last fix heading to — +14 min
  • Sat 24 Oct Max en route +9 min · last fix heading to — +9 min
  • Mon 2 Nov Max en route +25 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 8% · 2
  • On time 63% · 15
  • 3–10 min 17% · 4
  • 10–30 min 13% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
09:05on time +2 min
09:16 / 09:23≈ on time ≈ +2 min
09:44≈ on time ≈ +4 min
09:54≈ on time ≈ +4 min
10:09 / 10:16≈ on time ≈ +6 min
10:29≈ on time ≈ +7 min
10:39≈ on time ≈ +8 min
10:49 / 10:51≈ on time ≈ +9 min
10:57≈ on time ≈ +9 min
11:03 / 11:05≈ on time ≈ +10 min
11:08≈ on time ≈ +10 min
11:12 / 11:14≈ on time ≈ +11 min
11:28 / 11:30≈ +1 min ≈ +12 min
11:32 / 11:33≈ +1 min ≈ +12 min
11:35 / 11:36≈ +1 min ≈ +12 min
11:44 / 11:49≈ +1 min ≈ +12 min
11:51 / 11:52≈ +1 min ≈ +12 min
11:55+1 min +13 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:14+17 min+17 min
Fri 13 Nov— 11:59+1 min+16 min
Thu 12 Nov— 12:04+4 min+8 min
Wed 11 Nov— 11:59−1 min+23 min
Tue 10 Nov— 11:59+1 min+25 min
Mon 9 Nov— 11:590 min+30 min
Sun 8 Nov— 11:08+1 min+11 min
Sat 7 Nov— 11:14−2 min+24 min
Fri 6 Nov— 11:59+2 min+7 min
Thu 5 Nov— 11:14+1 min+11 min
Wed 4 Nov— 12:04−1 min+10 min
Tue 3 Nov— 12:040 min+9 min
Mon 2 Nov— 12:12+8 min+25 min
Sun 1 Nov— 12:040 min—
Sat 31 Oct— 12:26+22 min+23 min
Fri 30 Oct— 10:060 min+11 min
Thu 29 Oct— 12:04−1 min+36 min
Wed 28 Oct— 12:07+3 min+33 min
Tue 27 Oct— 12:18+14 min+49 min
Mon 26 Oct— 11:40+4 min+19 min
Sun 25 Oct— 12:05+1 min+5 min
Sat 24 Oct— 11:59+9 min+9 min
Fri 23 Oct— 11:16−2 min+5 min
Thu 22 Oct— 12:04−1 min—