812 1223 Kristianstad C – Trelleborg C

View line 812

Kristianstad C 14:04 → Trelleborg C 16:10 Daily 2 h 06 min · 23 stops Skånetrafiken

It has not run yet today

Last recorded run: Wednesday 4 November −3 min

Next service: today 14:04 from Kristianstad C · Thu 5 Nov

Next departure 14:04 today · Kristianstad C
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
81%
48/59 runs under 3 min
RT coverage: 59 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: +2 min

Last 30 days

Arrival delay at Trelleborg 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 23 Oct Max en route +28 min · last fix heading to — +28 min
  • Fri 28 Aug Max en route +22 min · last fix heading to — +20 min
  • Tue 25 Aug Max en route +13 min · last fix heading to — +11 min
  • Tue 8 Sept Max en route +11 min · last fix heading to — +11 min
  • Sat 8 Aug Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 49% · 29
  • On time 32% · 19
  • 3–10 min 12% · 7
  • 10–30 min 7% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 78% T n=9
  • 100% W n=12
  • 78% T n=9
  • 67% F n=9
  • 75% S n=8
  • 100% S n=4

Stops and timetable

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

Last 90 days, 59 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:046 min early 2 min early
14:10≈ 6 min early ≈ 2 min early
14:15≈ 6 min early ≈ 2 min early
14:26 / 14:28≈ 5 min early ≈ 1 min early
14:36≈ 4 min early ≈ 1 min early
14:40≈ 4 min early ≈ 1 min early
14:45 / 14:46≈ 4 min early ≈ on time
14:52≈ 4 min early ≈ 1 min early
14:58≈ 3 min early ≈ on time
15:04≈ 3 min early ≈ on time
15:07≈ 3 min early ≈ on time
15:12 / 15:19≈ 3 min early ≈ on time
15:21≈ 2 min early ≈ +1 min
15:24≈ 2 min early ≈ +2 min
15:27≈ 2 min early ≈ +2 min
15:30≈ 2 min early ≈ +2 min
15:36 / 15:38≈ 2 min early ≈ +3 min
15:41≈ 2 min early ≈ +3 min
15:45 / 15:46≈ 2 min early ≈ +3 min
15:50≈ 1 min early ≈ +4 min
15:56≈ 1 min early ≈ +5 min
15:59 / 16:00≈ 1 min early ≈ +5 min
16:101 min early +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
Wed 4 Nov— 16:18−3 min—
Sat 31 Oct— 16:210 min+3 min
Fri 30 Oct— 16:19−2 min—
Thu 29 Oct— 16:22+1 min+2 min
Wed 28 Oct— 16:24−2 min+6 min
Mon 26 Oct— 16:23+3 min+4 min
Fri 23 Oct— 16:31+28 min+28 min
Wed 21 Oct— 16:20−1 min+10 min
Tue 20 Oct— 16:200 min—
Sat 17 Oct— 16:000 min+3 min
Fri 16 Oct— 16:18−3 min—
Thu 15 Oct— 16:19−1 min—
Wed 14 Oct— 16:210 min—
Tue 13 Oct— 16:20−1 min—
Mon 12 Oct— 16:22+1 min+1 min
Sun 11 Oct— 16:18−3 min—
Sat 10 Oct— 16:19−2 min—
Fri 9 Oct— 16:220 min+3 min
Thu 8 Oct— 16:18−2 min—
Wed 7 Oct— 16:220 min+3 min
Mon 5 Oct— 16:20−1 min—
Sat 3 Oct— 16:220 min+2 min
Fri 2 Oct— 16:26+5 min+8 min
Thu 1 Oct— 16:21+1 min+1 min
Wed 30 Sept— 16:210 min—
Tue 29 Sept— 16:17−3 min—
Sun 27 Sept— 16:18−2 min—
Sat 26 Sept— 16:25+4 min+8 min
Thu 24 Sept— 16:200 min—
Wed 23 Sept— 16:18−3 min—