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

View line 803

København Østerport 18:05 → Växjö 20:51 Daily 2 h 46 min · 18 stops Skånetrafiken

Running now · updated 19:47

Heading to Växjö +1 min

Estimated arrival at Växjö 20:52 20:51 · 163 km/h

  1. København Østerport18:05
  2. Ørestad18:21
  3. Malmö Hyllie18:42
  4. Burlöv station19:02
  5. Eslöv station19:20
  6. Osby station20:05
  7. Växjö20:51

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

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

Last 30 days

Arrival delay at Växjö, 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 +66 min · last fix heading to — +61 min
  • Tue 17 Nov Max en route +46 min · last fix heading to — +27 min
  • Mon 16 Nov Max en route +47 min · last fix heading to — +25 min
  • Tue 27 Oct Max en route +42 min · last fix heading to — +25 min
  • Sat 14 Nov Max en route +36 min · last fix heading to — +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 41% · 12
  • 3–10 min 21% · 6
  • 10–30 min 34% · 10
  • 30+ min 3% · 1

On-time by weekday

  • 50% M n=4
  • 25% T n=4
  • 25% W n=4
  • 40% T n=5
  • 75% F n=4
  • 50% S n=4
  • 25% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (18 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
18:05on time +5 min
18:07 / 18:08≈ on time ≈ +5 min
18:11 / 18:14≈ on time ≈ +6 min
18:21 / 18:22≈ +1 min ≈ +7 min
18:24 / 18:25≈ +2 min ≈ +7 min
18:28 / 18:30≈ +2 min ≈ +7 min
18:42 / 18:48≈ +3 min ≈ +9 min
18:51≈ +4 min ≈ +9 min
18:55 / 18:57≈ +4 min ≈ +10 min
19:02≈ +4 min ≈ +10 min
19:09 / 19:11≈ +3 min ≈ +11 min
19:20≈ +4 min ≈ +12 min
19:30≈ +3 min ≈ +14 min
19:44 / 19:52≈ +3 min ≈ +15 min
20:05≈ +4 min ≈ +18 min
20:15≈ +5 min ≈ +20 min
20:37 / 20:40≈ +5 min ≈ +23 min
20:51+4 min +25 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+5 min+8 min
Wed 18 Nov— 21:54+61 min+66 min
Tue 17 Nov— 21:23+27 min+46 min
Mon 16 Nov— 21:22+25 min+47 min
Sun 15 Nov— 20:540 min+5 min
Sat 14 Nov— 21:14+18 min+36 min
Fri 13 Nov— 20:57+1 min+21 min
Thu 12 Nov— 20:54−1 min+21 min
Wed 11 Nov— 20:58+2 min+5 min
Tue 10 Nov— 20:54+1 min+6 min
Mon 9 Nov— 20:59+4 min+10 min
Sun 8 Nov— 21:04+8 min+28 min
Sat 7 Nov— 18:34+2 min+2 min
Fri 6 Nov— 20:58+2 min+5 min
Thu 5 Nov— 20:540 min+21 min
Wed 4 Nov— 21:14+14 min+18 min
Tue 3 Nov— 21:08+7 min+27 min
Mon 2 Nov— 21:03+2 min+5 min
Sun 1 Nov— 21:04+3 min+5 min
Sat 31 Oct— 21:01+1 min+22 min
Fri 30 Oct— 21:010 min+5 min
Thu 29 Oct— 21:06+4 min+22 min
Wed 28 Oct— 21:18+17 min+35 min
Tue 27 Oct— 21:26+25 min+42 min
Mon 26 Oct— 21:03+2 min+18 min
Sun 25 Oct— 20:43+11 min+12 min
Sat 24 Oct— 20:46+15 min+21 min
Fri 23 Oct— 20:05+12 min+18 min
Thu 22 Oct— 21:19+18 min+25 min