824 1586 Kävlinge station – Åstorp station

View line 824

Kävlinge station 23:14 → Åstorp station 23:50 Daily 0 h 36 min · 6 stops Skånetrafiken

It has not run yet today

Last recorded run: Saturday 7 November −1 min

Next service: today 23:14 from Kävlinge station · Tue 10 Nov

Next departure 23:14 today · Kävlinge station
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Åstorp station, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 19 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 68% · 19
  • On time 29% · 8
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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 10
23:143 min early 3 min early
23:23≈ 3 min early ≈ 2 min early
23:28≈ 3 min early ≈ 1 min early
23:35≈ 2 min early ≈ on time
23:42≈ 2 min early ≈ on time
23:502 min early +1 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 7 Nov— 23:54−1 min—
Wed 4 Nov— 23:54−2 min—
Mon 2 Nov— 00:04−1 min—
Sun 1 Nov— 23:59−2 min—
Sat 31 Oct— 23:58−1 min—
Fri 30 Oct— 00:03+1 min—
Wed 28 Oct— 00:010 min—
Sat 24 Oct— 23:59−2 min—
Fri 23 Oct— 23:59−1 min—
Wed 21 Oct— 23:56−3 min—
Tue 20 Oct— 00:03+3 min+3 min
Mon 19 Oct— 00:06+5 min+6 min
Wed 14 Oct— 23:57−3 min—
Tue 13 Oct— 23:57−3 min—
Sun 11 Oct— 23:57−3 min—
Mon 5 Oct— 00:000 min—
Sat 3 Oct— 23:58−2 min—
Tue 29 Sept— 00:00−3 min—
Sun 27 Sept— 00:00−1 min—
Sun 20 Sept— 00:00+1 min+2 min
Sat 19 Sept— 00:01−3 min—
Wed 2 Sept— 23:57−2 min—
Tue 1 Sept— 00:000 min—
Thu 27 Aug— 00:02+2 min+6 min
Fri 21 Aug— 23:57−3 min—
Thu 20 Aug— 23:56−3 min—
Tue 18 Aug— 23:57−3 min—
Fri 14 Aug— 23:59−1 min—
Wed 12 Aug— 23:42−3 min—