F38 81474 Lauterbourg – Woerth (Rhein)

View line F38

Lauterbourg 17:45 → Woerth (Rhein) 18:00 Daily 0 h 15 min · 6 stops SNCF

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 17:45 from Lauterbourg · Wed 18 Nov

Next departure 17:45 today · Lauterbourg
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
79/81 runs under 3 min
RT coverage: 81 full · 0 partial · 0 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 Woerth (Rhein), 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 25 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8064613 +5 min
  • Mon 31 Aug Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8064613 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 79
  • 3–10 min 2% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 100% T n=13
  • 100% W n=11
  • 100% T n=12
  • 92% F n=13
  • 100% S n=9
  • 100% S n=10

Stops and timetable

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

Last 90 days, 81 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
17:45on time on time
17:47 / 17:48≈ on time ≈ on time
17:50 / 17:51≈ on time ≈ on time
17:53 / 17:54≈ on time ≈ on time
17:57 / 17:58≈ on time ≈ on time
18:00on 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
Tue 17 NovWoerth (Rhein) 17:590 min—
Mon 16 NovWoerth (Rhein) 17:590 min—
Sun 15 NovWoerth (Rhein) 17:590 min—
Sat 14 NovWoerth (Rhein) 18:000 min—
Fri 13 NovWoerth (Rhein) 18:000 min—
Thu 12 NovWoerth (Rhein) 17:590 min—
Wed 11 NovWoerth (Rhein) 17:590 min—
Tue 10 NovWoerth (Rhein) 17:590 min—
Mon 9 NovWoerth (Rhein) 17:590 min—
Sun 8 NovWoerth (Rhein) 17:590 min—
Sat 7 NovWoerth (Rhein) 17:590 min—
Fri 6 NovWoerth (Rhein) 17:590 min—
Thu 5 NovWoerth (Rhein) 17:590 min—
Wed 4 NovWoerth (Rhein) 17:590 min—
Tue 3 NovWoerth (Rhein) 18:000 min—
Mon 2 NovWoerth (Rhein) 17:590 min—
Sun 1 NovWoerth (Rhein) 18:010 min—
Sat 31 OctWoerth (Rhein) 18:020 min—
Fri 30 OctWoerth (Rhein) 18:010 min—
Thu 29 OctWoerth (Rhein) 18:010 min—
Wed 28 OctWoerth (Rhein) 18:010 min—
Tue 27 OctWoerth (Rhein) 18:010 min—
Mon 26 OctWoerth (Rhein) 18:020 min—
Sun 25 OctWoerth (Rhein) 18:010 min—
Sat 24 OctWoerth (Rhein) 18:010 min—
Fri 23 OctWoerth (Rhein) 18:020 min—
Thu 22 OctWoerth (Rhein) 18:020 min—
Wed 21 OctWoerth (Rhein) 18:020 min—
Tue 20 OctWoerth (Rhein) 18:010 min—
Mon 19 OctWoerth (Rhein) 18:010 min—