812 1208 Trelleborg C – Kristianstad C

View line 812

Trelleborg C 06:50 → Kristianstad C 08:56 Daily 2 h 06 min · 23 stops Skånetrafiken

It has not run yet today

Last recorded run: Saturday 7 November −1 min

Next service: today 06:50 from Trelleborg C · Mon 9 Nov

Next departure 06:50 today · Trelleborg C
On-time · 30 days
71%
15/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
88%
57/65 runs under 3 min
RT coverage: 65 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Kristianstad 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

  • Sun 18 Oct Max en route +38 min · last fix heading to — +33 min
  • Wed 28 Oct Max en route +65 min · last fix heading to — +31 min
  • Tue 15 Sept Max en route +16 min · last fix heading to — +12 min
  • Wed 9 Sept Max en route +14 min · last fix heading to — +10 min
  • Thu 22 Oct Max en route +15 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 8% · 5
  • On time 80% · 52
  • 3–10 min 6% · 4
  • 10–30 min 3% · 2
  • 30+ min 3% · 2

On-time by weekday

  • 100% M n=11
  • 82% T n=11
  • 83% W n=12
  • 83% T n=12
  • 100% F n=9
  • 100% S n=7
  • 33% S n=3

Stops and timetable

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

Last 90 days, 65 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:501 min early on time
06:59 / 07:00≈ 1 min early ≈ on time
07:03≈ 1 min early ≈ on time
07:10≈ 1 min early ≈ +1 min
07:14 / 07:15≈ 1 min early ≈ +1 min
07:18≈ 1 min early ≈ +1 min
07:22 / 07:24≈ 1 min early ≈ +1 min
07:29≈ 1 min early ≈ +1 min
07:32≈ 1 min early ≈ +1 min
07:35≈ 1 min early ≈ +1 min
07:38≈ 1 min early ≈ +1 min
07:41 / 07:49≈ on time ≈ +1 min
07:53≈ on time ≈ +2 min
07:56≈ on time ≈ +2 min
08:01≈ on time ≈ +2 min
08:07≈ on time ≈ +2 min
08:13 / 08:14≈ on time ≈ +2 min
08:19≈ on time ≈ +3 min
08:23≈ on time ≈ +3 min
08:32 / 08:34≈ on time ≈ +3 min
08:45≈ on time ≈ +4 min
08:50≈ on time ≈ +4 min
08:56on time +4 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— 09:04−1 min—
Fri 6 Nov— 09:04+3 min+4 min
Thu 5 Nov— 09:04+3 min+7 min
Wed 4 Nov— 09:040 min—
Tue 3 Nov— 09:08+1 min+2 min
Mon 2 Nov— 09:070 min+2 min
Sun 1 Nov— 09:00+4 min+4 min
Sat 31 Oct— 09:06−1 min+2 min
Fri 30 Oct— 09:07+1 min+3 min
Thu 29 Oct— 09:070 min—
Wed 28 Oct— 09:38+31 min+65 min
Mon 26 Oct— 09:05−1 min—
Thu 22 Oct— 09:17+10 min+15 min
Tue 20 Oct— 09:08+1 min+7 min
Sun 18 Oct— 09:19+33 min+38 min
Fri 16 Oct— 09:07+1 min—
Thu 15 Oct— 09:06−1 min+3 min
Wed 14 Oct— 09:060 min+5 min
Tue 13 Oct— 09:12+5 min+10 min
Mon 12 Oct— 09:070 min+6 min
Sun 11 Oct— 09:05−1 min—
Sat 10 Oct— 09:060 min+5 min
Fri 9 Oct— 09:06−1 min—
Thu 8 Oct— 09:09+2 min+7 min
Wed 7 Oct— 09:07+1 min+6 min
Tue 6 Oct— 09:070 min—
Mon 5 Oct— 09:070 min+4 min
Thu 1 Oct— 09:070 min+5 min
Wed 30 Sept— 09:06+1 min+5 min
Tue 29 Sept— 09:06−1 min+4 min