F38 81471 Woerth (Rhein) – Lauterbourg

View line F38

Woerth (Rhein) 15:19 → Lauterbourg 15:36 Daily 0 h 17 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Lauterbourg at 15:36 0 min

  1. Woerth (Rhein)15:19
  2. Maximiliansau Im Ruesten15:21
  3. Hagenbach15:24
  4. Neuburg (Rhein)15:27
  5. Berg (Pfalz)15:30
  6. Lauterbourg15:36

Next service: tomorrow 15:19 from Woerth (Rhein) · Wed 18 Nov

Next departure 15:19 tomorrow · Woerth (Rhein)
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
43/44 runs under 3 min
RT coverage: 44 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

  • Tue 10 Nov Max en route +5 min · last fix heading to Lauterbourg +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 44 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:19on time on time
15:21 / 15:22≈ on time ≈ on time
15:24 / 15:25≈ on time ≈ on time
15:27 / 15:28≈ on time ≈ on time
15:30 / 15:31≈ on time ≈ on time
15:36on 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 15:370 min—
Mon 16 NovLauterbourg 15:380 min—
Sun 15 NovLauterbourg 15:370 min—
Sat 14 NovLauterbourg 15:380 min—
Thu 12 NovLauterbourg 15:370 min—
Wed 11 NovLauterbourg 15:370 min—
Tue 10 NovLauterbourg 15:42+5 min+5 min
Mon 9 NovLauterbourg 15:370 min—
Sun 8 NovLauterbourg 15:370 min—
Sat 7 NovLauterbourg 15:370 min—
Fri 6 NovLauterbourg 15:370 min—
Thu 5 NovLauterbourg 15:370 min—
Wed 4 NovLauterbourg 15:370 min—
Tue 3 NovLauterbourg 15:380 min—
Mon 2 NovLauterbourg 15:370 min—
Sun 1 NovLauterbourg 15:370 min—
Sat 31 OctLauterbourg 15:380 min—
Fri 30 OctLauterbourg 15:370 min—
Thu 29 OctLauterbourg 15:370 min—
Wed 28 OctLauterbourg 15:370 min—
Tue 27 OctLauterbourg 15:370 min—
Mon 26 OctLauterbourg 15:380 min—
Sun 25 OctLauterbourg 15:370 min—
Sat 24 OctLauterbourg 15:370 min—
Fri 23 OctLauterbourg 15:370 min—
Thu 22 OctLauterbourg 15:370 min—
Wed 21 OctLauterbourg 15:370 min—
Tue 20 OctLauterbourg 15:370 min—
Mon 19 OctLauterbourg 15:380 min—
Sun 18 OctLauterbourg 15:370 min—