F38 81443 Woerth (Rhein) – Lauterbourg

View line F38

Woerth (Rhein) 05:25 → Lauterbourg 05:42 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Lauterbourg at 05:42 0 min

  1. Woerth (Rhein)05:25
  2. Maximiliansau Im Ruesten05:27
  3. Hagenbach05:30
  4. Neuburg (Rhein)05:34
  5. Berg (Pfalz)05:37
  6. Lauterbourg05:42

Next service: tomorrow 05:25 from Woerth (Rhein) · Fri 20 Nov

Next departure 05:25 tomorrow · Woerth (Rhein)
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Lauterbourg +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
05:25on time on time
05:27 / 05:28≈ on time ≈ on time
05:30 / 05:31≈ on time ≈ on time
05:34 / 05:35≈ on time ≈ on time
05:37 / 05:38≈ on time ≈ on time
05:42on 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
Thu 19 NovLauterbourg 05:430 min—
Wed 18 NovLauterbourg 05:430 min—
Tue 17 NovLauterbourg 05:430 min—
Mon 16 NovLauterbourg 05:430 min—
Fri 13 NovLauterbourg 05:430 min—
Thu 12 NovLauterbourg 05:430 min—
Wed 11 NovLauterbourg 05:430 min—
Tue 10 NovLauterbourg 05:440 min—
Mon 9 NovLauterbourg 05:430 min—
Fri 6 NovLauterbourg 05:430 min—
Thu 5 NovLauterbourg 05:430 min—
Wed 4 NovLauterbourg 05:430 min—
Tue 3 NovLauterbourg 05:430 min—
Mon 2 NovLauterbourg 05:430 min—
Fri 30 OctLauterbourg 05:430 min—
Thu 29 OctLauterbourg 05:430 min—
Wed 28 OctLauterbourg 05:430 min—
Tue 27 OctLauterbourg 05:440 min—
Mon 26 OctLauterbourg 05:430 min—
Fri 23 OctLauterbourg 05:430 min—
Thu 22 OctLauterbourg 05:430 min—
Wed 21 OctLauterbourg 05:430 min—
Tue 20 OctLauterbourg 05:430 min—
Mon 19 OctLauterbourg 05:430 min—
Fri 16 OctLauterbourg 05:440 min—
Thu 15 OctLauterbourg 05:430 min—
Wed 14 OctLauterbourg 05:430 min—
Tue 13 OctLauterbourg 05:430 min—
Mon 12 OctLauterbourg 05:430 min—
Fri 9 OctLauterbourg 05:48+5 min+5 min