R22 5909 Bonfol – Porrentruy

View line R22

Bonfol 07:13 → Porrentruy 07:27 Sat, Sun 0 h 14 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Porrentruy at 07:27 0 min

  1. Bonfol07:13
  2. Vendlincourt07:16
  3. Alle07:21
  4. Porrentruy07:27

Next service: Saturday 07:13 from Bonfol · Sat 21 Nov

Next departure 07:13 Saturday · Bonfol
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 8% · 3
  • On time 92% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=4
  • 100% F n=4
  • 100% S n=10
  • 100% S n=11

Stops and timetable

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

Last 90 days, 39 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
07:13on time on time
07:16≈ on time ≈ on time
07:21 / 07:22≈ on time ≈ on time
07:27on 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
Sun 15 NovPorrentruy 07:280 min—
Sat 14 NovPorrentruy 07:280 min—
Sun 8 NovPorrentruy 07:28−1 min—
Sat 7 NovPorrentruy 07:280 min—
Sun 1 NovPorrentruy 07:280 min—
Sat 31 OctPorrentruy 07:280 min—
Sat 24 OctPorrentruy 07:280 min—
Sun 18 OctPorrentruy 07:280 min—
Sat 17 OctPorrentruy 07:280 min—
Sun 11 OctPorrentruy 07:280 min—
Sat 10 OctPorrentruy 07:30+1 min+1 min
Mon 5 OctPorrentruy 07:29No data—
Sun 4 OctPorrentruy 07:290 min—
Sat 3 OctPorrentruy 07:270 min—
Fri 2 OctPorrentruy 07:26No data—
Thu 1 OctPorrentruy 06:260 min—
Wed 30 SeptPorrentruy 06:260 min—
Tue 29 SeptPorrentruy 19:26No data—
Mon 28 SeptPorrentruy 19:26−1 min—
Sun 27 SeptPorrentruy 19:260 min—
Sat 26 SeptPorrentruy 19:260 min—
Fri 25 SeptPorrentruy 19:26−22 min—
Thu 24 SeptPorrentruy 17:26No data—
Mon 21 SeptPorrentruy 11:260 min—
Sun 20 SeptPorrentruy 11:260 min—
Mon 14 SeptPorrentruy 11:260 min—
Sun 13 SeptPorrentruy 11:260 min—
Fri 11 SeptPorrentruy 11:26−1 min—
Thu 10 SeptPorrentruy 06:260 min—
Wed 9 SeptPorrentruy 06:260 min—