812 1288 Trelleborg C → Lund C

View line 812

Trelleborg C 22:20 → Lund C 23:11 Daily 0 h 51 min · 12 stops Skånetrafiken

Regional 1288 Trelleborg C–Lund C: final delay under 3 min on 13 of its 19 runs with data in the last 30 days (68%). Median final delay: +1 min. Running now, 1 min early. Expected at Lund C: 23:11. TrainsRadar data as of 22 Nov 2026, 23:08 (GMT+1).

Running now · updated 23:08

Heading to Lund C −1 min

Estimated arrival at Lund C 23:11 · 34 km/h

  1. Trelleborg C22:20
  2. Västra Ingelstad station22:33
  3. Malmö Hyllie22:44
  4. Malmö C22:52
  5. Burlöv station22:59
  6. Hjärup station23:05
  7. Lund C23:11

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

On-time · 30 days
68%
13/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
81%
42/52 runs under 3 min
RT coverage: 52 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Lund C, 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 +20 min · last fix heading to — +19 min
  • Thu 12 Nov Max en route +10 min · last fix heading to — +10 min
  • Tue 15 Sept Max en route +8 min · last fix heading to — +8 min
  • Mon 16 Nov Max en route +9 min · last fix heading to — +7 min
  • Sun 13 Sept Max en route +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 77% · 40
  • 3–10 min 15% · 8
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 60% T n=5
  • 86% W n=7
  • 67% T n=6
  • 91% F n=11
  • 88% S n=8
  • 75% S n=8

Stops and timetable

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

Last 90 days, 52 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
22:202 min early +1 min
22:29 / 22:30≈ 2 min early ≈ +1 min
22:33≈ 1 min early ≈ +1 min
22:40≈ 1 min early ≈ +2 min
22:44 / 22:45≈ 1 min early ≈ +2 min
22:49≈ on time ≈ +2 min
22:52 / 22:54≈ on time ≈ +3 min
22:59≈ on time ≈ +4 min
23:02≈ on time ≈ +4 min
23:05≈ +1 min ≈ +5 min
23:08≈ +1 min ≈ +5 min
23:11+1 min +6 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
Sun 22 Nov— 23:04−1 min—
Sat 21 Nov— 23:19+1 min+2 min
Fri 20 Nov— 23:19+1 min+1 min
Thu 19 Nov— 23:190 min—
Mon 16 Nov— 23:23+7 min+9 min
Sun 15 Nov— 23:14+1 min+4 min
Fri 13 Nov— 23:14+1 min+1 min
Thu 12 Nov— 23:24+10 min+10 min
Wed 11 Nov— 23:140 min+1 min
Tue 10 Nov— 23:24+4 min+5 min
Mon 9 Nov— 23:18+2 min+2 min
Sat 7 Nov— 23:14+1 min+1 min
Fri 6 Nov— 23:19+1 min—
Thu 5 Nov— 23:23+2 min+2 min
Mon 2 Nov— 23:190 min+1 min
Sat 31 Oct— 23:39+19 min+20 min
Fri 30 Oct— 23:26+6 min+6 min
Thu 29 Oct— 23:25+4 min+4 min
Sun 25 Oct— 23:23+2 min+2 min
Thu 22 Oct— 23:210 min—
Sun 18 Oct— 23:21+1 min—
Sat 17 Oct— 23:21+1 min—
Fri 16 Oct— 23:22+2 min+2 min
Wed 14 Oct— 23:20−1 min—
Tue 13 Oct— 23:210 min—
Sat 10 Oct— 23:22+2 min+2 min
Fri 9 Oct— 23:200 min—
Tue 6 Oct— 23:210 min—
Mon 5 Oct— 23:200 min—
Sun 4 Oct— 23:21+1 min—