F38 81454 Lauterbourg – Woerth (Rhein)

View line F38

Lauterbourg 09:21 → Woerth (Rhein) 09:38 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Woerth (Rhein) at 09:38 0 min

  1. Lauterbourg09:21
  2. Berg (Pfalz)09:23
  3. Neuburg (Rhein)09:26
  4. Hagenbach09:29
  5. Maximiliansau Im Ruesten09:34
  6. Woerth (Rhein)09:38

Next service: tomorrow 09:21 from Lauterbourg · Thu 19 Nov

Next departure 09:21 tomorrow · Lauterbourg
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 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=6
  • 100% 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, 33 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
09:21on time on time
09:23 / 09:24≈ on time ≈ on time
09:26 / 09:27≈ on time ≈ on time
09:29 / 09:30≈ on time ≈ on time
09:34 / 09:35≈ on time ≈ on time
09:38on 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
Wed 18 NovWoerth (Rhein) 09:390 min—
Tue 17 NovWoerth (Rhein) 09:390 min—
Mon 16 NovWoerth (Rhein) 09:390 min—
Fri 13 NovWoerth (Rhein) 09:390 min—
Thu 12 NovWoerth (Rhein) 09:390 min—
Wed 11 NovWoerth (Rhein) 09:390 min—
Tue 10 NovWoerth (Rhein) 09:390 min—
Mon 9 NovWoerth (Rhein) 09:390 min—
Fri 6 NovWoerth (Rhein) 09:390 min—
Thu 5 NovWoerth (Rhein) 09:390 min—
Wed 4 NovWoerth (Rhein) 09:390 min—
Tue 3 NovWoerth (Rhein) 09:400 min—
Mon 2 NovWoerth (Rhein) 09:390 min—
Fri 30 OctWoerth (Rhein) 09:390 min—
Thu 29 OctWoerth (Rhein) 09:390 min—
Wed 28 OctWoerth (Rhein) 09:390 min—
Tue 27 OctWoerth (Rhein) 09:390 min—
Mon 26 OctWoerth (Rhein) 09:390 min—
Fri 23 OctWoerth (Rhein) 09:390 min—
Thu 22 OctWoerth (Rhein) 09:390 min—
Wed 21 OctWoerth (Rhein) 09:390 min—
Tue 20 OctWoerth (Rhein) 09:390 min—
Mon 19 OctWoerth (Rhein) 09:390 min—
Fri 16 OctWoerth (Rhein) 09:390 min—
Thu 15 OctWoerth (Rhein) 09:390 min—
Wed 14 OctWoerth (Rhein) 09:390 min—
Tue 13 OctWoerth (Rhein) 09:390 min—
Mon 12 OctWoerth (Rhein) 09:400 min—
Fri 9 OctWoerth (Rhein) 09:400 min—
Thu 8 OctWoerth (Rhein) 09:390 min—