R2 5958 Delémont – Porrentruy

View line R2

Delémont 16:21 → Porrentruy 16:50 Daily 0 h 29 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Porrentruy at 16:52 +2 min

  1. Delémont16:21
  2. Courtételle16:24
  3. Courfaivre16:26
  4. Glovelier16:33
  5. St-Ursanne16:37
  6. Courgenay16:43
  7. Porrentruy16:50

Next service: tomorrow 16:21 from Delémont · Fri 6 Nov

Next departure 16:21 tomorrow · Delémont
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Worst days

  • Fri 16 Oct Max en route +8 min · last fix heading to Porrentruy +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 39
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 75% F n=4
  • 100% S n=4
  • 100% S n=8

Stops and timetable

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

Last 90 days, 40 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
16:21on time on time
16:24≈ on time ≈ on time
16:26≈ on time ≈ on time
16:30≈ on time ≈ on time
16:33≈ on time ≈ on time
16:37≈ on time ≈ on time
16:43 / 16:44≈ on time ≈ on time
16:50on time 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
Thu 5 NovPorrentruy 06:53+2 min+2 min
Wed 4 NovPorrentruy 06:490 min—
Tue 3 NovPorrentruy 06:49−1 min—
Mon 2 NovPorrentruy 06:490 min—
Sun 1 NovBonfol 07:090 min—
Sat 31 OctBonfol 07:090 min—
Fri 30 OctPorrentruy 06:52+1 min—
Thu 29 OctPorrentruy 06:510 min—
Wed 28 OctPorrentruy 06:510 min—
Tue 27 OctPorrentruy 06:500 min—
Mon 26 OctPorrentruy 06:500 min—
Sun 25 OctBonfol 07:090 min+3 min
Sat 24 OctBonfol 07:090 min—
Fri 23 OctPorrentruy 06:50−1 min—
Thu 22 OctPorrentruy 06:51−1 min—
Wed 21 OctPorrentruy 06:50−1 min—
Tue 20 OctPorrentruy 06:51−1 min—
Mon 19 OctPorrentruy 06:51−1 min—
Sun 18 OctBonfol 07:100 min—
Sat 17 OctBonfol 07:100 min—
Fri 16 OctPorrentruy 06:59+8 min+8 min
Thu 15 OctPorrentruy 06:52+1 min—
Wed 14 OctPorrentruy 06:510 min—
Tue 13 OctPorrentruy 06:50−1 min—
Mon 12 OctPorrentruy 06:500 min—
Sun 11 OctBonfol 07:100 min—
Sat 10 OctBonfol 07:12+3 min+3 min
Fri 9 OctPorrentruy 06:510 min—
Thu 8 OctPorrentruy 06:52+1 min—
Wed 7 OctPorrentruy 06:510 min—