RE 4130 Fribourg/Freiburg – Romont FR

View line RE

Fribourg/Freiburg 18:16 → Romont FR 18: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 18:38 0 min

  1. Fribourg/Freiburg18:16
  2. Romont FR18:38

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

Next departure 18: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
100%
68/68 runs under 3 min
RT coverage: 68 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 16% · 11
  • On time 84% · 57
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=11
  • 100% W n=10
  • 100% T n=10
  • 100% F n=11
  • 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, 68 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
18:16on time on time
18:38on time +2 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 19 NovRomont FR 18:390 min—
Wed 18 NovRomont FR 18:37−2 min+2 min
Tue 17 NovRomont FR 18:38−1 min+1 min
Mon 16 NovRomont FR 18:39+2 min+2 min
Sun 15 NovAarau 11:49+1 min+1 min
Sat 14 NovAarau 11:490 min—
Fri 13 NovRomont FR 18:38−1 min—
Thu 12 NovRomont FR 18:390 min—
Wed 11 NovRomont FR 18:39+1 min+2 min
Tue 10 NovRomont FR 18:37−1 min+1 min
Mon 9 NovRomont FR 18:390 min—
Sun 8 NovAarau 11:49+1 min—
Sat 7 NovAarau 11:490 min—
Fri 6 NovRomont FR 18:38−1 min+2 min
Thu 5 NovRomont FR 18:38−1 min—
Wed 4 NovRomont FR 18:38−1 min—
Tue 3 NovRomont FR 18:390 min—
Mon 2 NovRomont FR 18:37−2 min—
Sun 1 NovAarau 11:49−1 min—
Sat 31 OctAarau 11:500 min—
Fri 30 OctRomont FR 18:38−1 min—
Thu 29 OctRomont FR 18:38−1 min—
Wed 28 OctRomont FR 18:42+2 min+2 min
Tue 27 OctSpeicher 14:02+1 min+1 min
Mon 26 OctRomont FR 18:37−2 min—
Sun 25 OctAarau 11:51+2 min+2 min
Sat 24 OctAarau 11:51+2 min+2 min
Fri 23 OctRomont FR 18:40+1 min—
Thu 22 OctRomont FR 18:38−1 min—
Wed 21 OctRomont FR 18:37−1 min+2 min