823 1922 Hässleholm C – Markaryd station

View line 823

Hässleholm C 15:42 → Markaryd station 16:09 Daily 0 h 27 min · 4 stops Skånetrafiken

✓ Today’s run finished

Today, last fix heading to — at 16:13 −1 min

  1. Hässleholm C15:42
  2. Bjärnum station15:52
  3. Vittsjö station15:58
  4. Markaryd station16:09

Next service: tomorrow 15:42 from Hässleholm C · Fri 6 Nov

Next departure 15:42 tomorrow · Hässleholm C
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 0 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 47 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: +1 min

Last 30 days

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

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

Distribution · 90 days

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

  • Early 49% · 23
  • On time 51% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 47 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
15:422 min early on time
15:52 / 15:53≈ 1 min early ≈ on time
15:58 / 15:59≈ 1 min early ≈ on time
16:091 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
Thu 5 Nov— 16:13−1 min—
Tue 3 Nov— 16:190 min+4 min
Sun 1 Nov— 16:190 min+4 min
Sat 31 Oct— 16:17−1 min—
Mon 26 Oct— 16:17−1 min—
Sun 25 Oct— 16:21+2 min+3 min
Sat 24 Oct— 16:180 min—
Thu 22 Oct— 16:18−1 min+3 min
Tue 20 Oct— 16:18−1 min+3 min
Mon 19 Oct— 16:18−1 min—
Sun 18 Oct— 16:17−1 min—
Thu 15 Oct— 16:19+1 min—
Mon 12 Oct— 16:18−1 min—
Fri 9 Oct— 16:18−1 min—
Thu 8 Oct— 16:18−1 min—
Wed 7 Oct— 16:20+1 min+3 min
Mon 5 Oct— 16:18−1 min—
Sat 3 Oct— 16:190 min+4 min
Wed 30 Sept— 16:190 min+3 min
Tue 29 Sept— 16:17−1 min+3 min
Mon 28 Sept— 16:18−1 min+3 min
Fri 25 Sept— 16:18−1 min+3 min
Sat 19 Sept— 16:18−2 min—
Fri 18 Sept— 16:18−1 min+3 min
Tue 15 Sept— 16:17−2 min+3 min
Fri 11 Sept— 16:190 min—
Wed 9 Sept— 16:18−1 min+3 min
Tue 8 Sept— 16:20+2 min+8 min
Mon 7 Sept— 16:21+1 min+8 min
Sun 6 Sept— 16:270 min+3 min