R11 5827 Delle → Porrentruy

View line R11

Delle 15:42 → Porrentruy 15:58 Daily 0 h 16 min · 6 stops SBB CFF FFS

R11 5827 Delle–Porrentruy: final delay under 3 min on 27 of its 27 runs with data in the last 30 days (100%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 15:13 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November −1 min

Next service: today 15:42 from Delle · Sun 22 Nov

Next departure 15:42 today · Delle
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 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
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Porrentruy, 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 2% · 1
  • On time 98% · 46
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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:42on time on time
15:44≈ on time ≈ on time
15:46≈ on time ≈ on time
15:51≈ on time ≈ on time
15:54≈ 1 min early ≈ on time
15:581 min early on time

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 21 NovPorrentruy 15:58−1 min—
Fri 20 NovPorrentruy 15:58−1 min—
Thu 19 NovPorrentruy 15:590 min—
Wed 18 NovPorrentruy 15:58−1 min—
Tue 17 NovPorrentruy 15:59−1 min—
Mon 16 NovPorrentruy 15:58−1 min—
Fri 13 NovPorrentruy 15:58−1 min—
Thu 12 NovPorrentruy 15:58−1 min—
Wed 11 NovPorrentruy 15:58−1 min—
Tue 10 NovPorrentruy 15:58−1 min—
Mon 9 NovPorrentruy 15:590 min—
Sun 8 NovPorrentruy 15:59−1 min—
Sat 7 NovPorrentruy 15:590 min—
Fri 6 NovPorrentruy 15:58−1 min—
Thu 5 NovPorrentruy 15:58−1 min—
Wed 4 NovPorrentruy 15:58−1 min—
Tue 3 NovPorrentruy 15:58−1 min—
Mon 2 NovPorrentruy 15:59−1 min—
Sun 1 NovPorrentruy 15:58−1 min—
Sat 31 OctPorrentruy 15:58−1 min—
Fri 30 OctPorrentruy 15:58−1 min—
Thu 29 OctPorrentruy 16:01+2 min+2 min
Wed 28 OctPorrentruy 15:58−1 min—
Tue 27 OctPorrentruy 15:59−1 min—
Mon 26 OctPorrentruy 15:59−1 min—
Sun 25 OctPorrentruy 15:580 min—
Sat 24 OctPorrentruy 15:590 min—
Fri 23 OctPorrentruy 15:58−1 min—
Thu 22 OctPorrentruy 15:59−1 min—
Wed 21 OctPorrentruy 15:58−1 min—