F38 81441 Woerth (Rhein) – Lauterbourg

View line F38

Woerth (Rhein) 04:39 → Lauterbourg 04:50 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 2 stops SNCF

✓ Today’s run finished

Today it reached Lauterbourg at 04:50 0 min

  1. Woerth (Rhein)04:39
  2. Lauterbourg04:50

Next service: tomorrow 04:39 from Woerth (Rhein) · Wed 18 Nov

Next departure 04:39 tomorrow · Woerth (Rhein)
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 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 Lauterbourg, in minutes. One bar per run.

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

Worst days

  • Wed 21 Oct Max en route +10 min · last fix heading to Lauterbourg +10 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 88% W n=8
  • 100% T n=9
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 46 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
04:39on time on time
04:50on 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 NovLauterbourg 04:490 min—
Mon 16 NovLauterbourg 04:490 min—
Fri 13 NovLauterbourg 04:490 min—
Thu 12 NovLauterbourg 04:490 min—
Wed 11 NovLauterbourg 04:490 min—
Tue 10 NovLauterbourg 04:490 min—
Mon 9 NovLauterbourg 04:490 min—
Fri 6 NovLauterbourg 04:490 min—
Thu 5 NovLauterbourg 04:490 min—
Wed 4 NovLauterbourg 04:490 min—
Tue 3 NovLauterbourg 04:490 min—
Mon 2 NovLauterbourg 04:490 min—
Fri 30 OctLauterbourg 04:510 min—
Thu 29 OctLauterbourg 04:510 min—
Wed 28 OctLauterbourg 04:510 min—
Tue 27 OctLauterbourg 04:520 min—
Mon 26 OctLauterbourg 04:510 min—
Fri 23 OctLauterbourg 04:510 min—
Thu 22 OctLauterbourg 04:510 min—
Wed 21 OctLauterbourg 05:01+10 min+10 min
Tue 20 OctLauterbourg 04:510 min—
Mon 19 OctLauterbourg 04:510 min—
Fri 16 OctLauterbourg 04:510 min—
Thu 15 OctLauterbourg 04:510 min—
Wed 14 OctLauterbourg 04:510 min—
Tue 13 OctLauterbourg 04:510 min—
Mon 12 OctLauterbourg 04:510 min—
Thu 8 OctLauterbourg 04:510 min—
Wed 7 OctLauterbourg 04:510 min—
Tue 6 OctLauterbourg 04:510 min—