F38 81470 Lauterbourg – Woerth (Rhein)

View line F38

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 15:45 from Lauterbourg · Tue 17 Nov

Next departure 15:45 today · Lauterbourg
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
95%
35/37 runs under 3 min
RT coverage: 37 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

  • Sun 30 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8019103 +20 min
  • Sun 23 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8019103 +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 35
  • 3–10 min 0% · 0
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=2
  • 50% S n=4

Stops and timetable

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

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