812 1224 Trelleborg C – Kristianstad C

View line 812

Trelleborg C 14:50 → Kristianstad C 16:56 Daily 2 h 06 min · 20 stops Skånetrafiken

It has not run yet today

Last recorded run: Saturday 7 November 0 min

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

Next departure 14:50 today · Trelleborg C
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
85%
46/54 runs under 3 min
RT coverage: 54 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +12 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

  • Fri 16 Oct Max en route +40 min · last fix heading to — +37 min
  • Wed 14 Oct Max en route +35 min · last fix heading to — +32 min
  • Thu 17 Sept Max en route +33 min · last fix heading to — +27 min
  • Mon 5 Oct Max en route +16 min · last fix heading to — +11 min
  • Wed 30 Sept Max en route +10 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 7% · 4
  • On time 78% · 42
  • 3–10 min 7% · 4
  • 10–30 min 4% · 2
  • 30+ min 4% · 2

On-time by weekday

  • 83% M n=6
  • 100% T n=7
  • 63% W n=8
  • 63% T n=8
  • 88% F n=8
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

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