RE 4126 Fribourg/Freiburg – Romont FR

View line RE

Fribourg/Freiburg 16:16 → Romont FR 16:38 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 2 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Romont FR at 16:38 0 min

  1. Fribourg/Freiburg16:16
  2. Romont FR16:38

Next service: tomorrow 16:16 from Fribourg/Freiburg · Fri 6 Nov

Next departure 16:16 tomorrow · Fribourg/Freiburg
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
42/43 runs under 3 min
RT coverage: 43 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 Romont FR, in minutes. One bar per run.

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

Worst days

  • Mon 5 Oct Max en route +4 min · last fix heading to Aarau +4 min

Distribution · 90 days

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

  • Early 19% · 8
  • On time 79% · 34
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 43 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:16on time on time
16:38on time +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 NovRomont FR 16:390 min—
Wed 4 NovRomont FR 16:38−1 min—
Tue 3 NovRomont FR 16:38−1 min—
Mon 2 NovRomont FR 16:42+3 min+3 min
Sun 1 NovAarau 10:500 min—
Sat 31 OctAarau 10:500 min+1 min
Fri 30 OctRomont FR 16:390 min+1 min
Thu 29 OctRomont FR 16:390 min—
Wed 28 OctRomont FR 16:37−2 min+1 min
Tue 27 OctRomont FR 16:38−1 min—
Mon 26 OctRomont FR 16:400 min—
Sun 25 OctAarau 10:50+2 min+2 min
Sat 24 OctAarau 10:500 min+1 min
Fri 23 OctRomont FR 16:380 min—
Thu 22 OctRomont FR 16:36−3 min—
Wed 21 OctRomont FR 16:38−1 min—
Tue 20 OctRomont FR 16:390 min—
Mon 19 OctRomont FR 16:38−1 min—
Sun 18 OctAarau 10:500 min—
Sat 17 OctAarau 10:51+1 min+2 min
Fri 16 OctRomont FR 16:38−2 min+2 min
Thu 15 OctRomont FR 16:390 min—
Wed 14 OctRomont FR 16:41+2 min+2 min
Tue 13 OctRomont FR 16:38−1 min+1 min
Mon 12 OctRomont FR 16:36−3 min+2 min
Sun 11 OctAarau 10:500 min—
Sat 10 OctAarau 10:500 min—
Fri 9 OctAarau 10:49−1 min+1 min
Thu 8 OctAarau 10:51+1 min+2 min
Wed 7 OctAarau 10:50+1 min—