A bridge carries traffic while giving travelers an alternative to another crossing, a service whose value becomes easier to appreciate when one connection is no longer available. On an ordinary day, traffic can be counted fairly straightforwardly; the contribution of the alternative is harder to observe, even when it helps the network function.
Mannheim and Ludwigshafen provide a useful case because the two German cities face each other across the Rhine, which also forms the boundary between Baden-Württemberg and Rhineland-Palatinate. Their labor markets overlap extensively, while their road networks connect through a small number of crossings, two of which serve the central urban area. Since early August 2026, damage at the Ludwigshafen bridgehead has closed the northern of these, the Kurt Schumacher Bridge, to motor vehicles.
The tempting question is how much this closure costs. The available evidence supports a more useful starting point: which relationships depend on the crossing, what would have to happen for the remaining network to absorb its traffic, and which outcomes would distinguish successful adaptation from a loss of access?
Those questions lead to a different assessment than either a dramatic congestion forecast or a reassuring photograph of an empty road. Almost 29,000 recorded commuting relationships connect the two cities. Dependence on the neighboring labor market is markedly asymmetric. And even substantial diversion away from the remaining central road bridge could leave it with a large additional daily traffic load. None of these findings, however, identifies the closure's realized economic cost.
Several ways across, one road link missing
Lines show connections; width does not encode capacity.
Show compact values
| Connection | Status |
|---|---|
| A6 / Theodor Heuss | Road · diversion |
| Kurt Schumacher | Road + tram · closed |
| Kurt Schumacher | Walk + cycle · open |
| Konrad Adenauer | Road · alternative |
| Rail corridor | Crossing available |
Enlarge chart
Scroll the full chart horizontally and vertically.
Exact values, units and download
| link | mode | status | since | source |
|---|---|---|---|---|
| Kurt-Schumacher-Brücke | Kfz | gesperrt | 2026-08-05 | S01 |
| Kurt-Schumacher-Brücke | Straßenbahn | gesperrt | 2026-06-01 | S01 |
| Kurt-Schumacher-Brücke | Fuß / Rad | offen | 2026-08-05 | S01 |
| Konrad-Adenauer-Korridor | Kfz | Ausweichquerung; Zufahrten teils eingeschränkt | 2026-09-04 | S01;S02 |
| Konrad-Adenauer-Korridor | Schiene | Rheinquerung bleibt möglich | 2026-09-04 | S01;S05 |
| A6 / Theodor-Heuss-Brücke | Kfz | großräumige Umleitung | 2026-08-05 | S01 |
The missing connection is specific
The closure concerns the Kurt Schumacher Bridge and its northern bridgehead in Ludwigshafen. Tram services across that bridge had already stopped in June. Walking and cycling remain possible. The Konrad Adenauer Bridge provides the other central road crossing; the A6 and its Theodor Heuss Bridge provide a northern alternative. Rail has separate crossing infrastructure. A lost road connection therefore changes the network differently for different modes. City of Mannheim, July 30, 2026
The surrounding network has also been changing, with Ludwigshafen's rebuilt southern elevated road opening to traffic on July 4. Further connections became available during August, including the Mundenheimer Straße access ramp on August 31, while other work and restrictions continued. The treatment in a before-and-after study would consequently be a sequence of network changes, unless the analyst took care to separate them. Ludwigshafen construction updates
This matters for the counterfactual. Continuing to operate an unsafe structure is not an economically meaningful policy alternative. The relevant comparisons concern different safe construction schedules, access arrangements and replacement services. An estimate that treats an unsafe bridge remaining open as an available option would begin with the wrong decision problem.
Start with the accounting
An account of normal traffic volumes reported by SWR, attributed to Mannheim's construction administration, places the two central road bridges at approximately 120,000 vehicles per day in total. About 55,000 used the northern crossing, implying a southern reference volume of about 65,000. The north therefore represented roughly 46 percent of these two bridges' combined reference traffic. This is not a measure of regional road capacity. SWR traffic report
Suppose half of the former northern passages join the southern crossing. Suppose the other half is accommodated outside that southern daily vehicle total, through other routes, other modes, or trips no longer made. The south would then carry 65,000 plus 27,500 passages: 92,500 in total, an increase of about 42 percent over the reference.
Half the northern flow means 42% more in the south
“Elsewhere”: other routes, modes or foregone trips; not simply a change of time on the same day.
Show compact values
| Scenario · 50% elsewhere | Vehicles/day |
|---|---|
| Southern reference | 65,000 |
| Additional from north | 27,500 |
| Southern scenario total | 92,500 |
| Accommodated elsewhere | 27,500 |
Enlarge chart
Scroll the full chart horizontally and vertically.
Elsewhere: 27.500 · Both bars: 0–120,000 vehicles/day.
Exact values, units and download
| origin | destination | vehicles_day | status |
|---|---|---|---|
| Nordkorridor: frühere Fahrten | Südkorridor: angenommene Zusatzmenge | 27500.00000000 | scenario |
| Nordkorridor: frühere Fahrten | andere Route / Verkehrsmittel / entfallene Fahrt | 27500.00000000 | scenario |
| Südkorridor: Referenz | Südkorridor: bisherige Menge | 65000.00000000 | reference-derived |
The calculation conserves traffic within an explicitly defined scenario, without estimating where drivers have actually gone or how much additional travel time 92,500 passages would produce. Daily volumes cannot reveal the concentration of demand within the peak, the effect of an intersection, or the amount of usable road capacity. Those require observations and a calibrated network model.
The accounting nevertheless disciplines the discussion. Although finding another solution for half the displaced traffic sounds substantial, the half that remains is also substantial relative to the southern crossing's previous load. The accounting makes the relationship between these two quantities explicit.
Reverse the calculation and it becomes a question for traffic management. If the southern daily total is to remain within 30 percent of its reference, approximately 64.5 percent of former northern passages must be accommodated outside that total. At a 20 percent increase, the required share rises to 76.4 percent. These are conditions set by the reader, not engineering limits inferred from the data.
A diversion target has an arithmetic cost
The increase is a chosen condition, not an observed capacity limit.
Show compact values
| Southern increase | Required elsewhere |
|---|---|
| 0 % | 100.0 % |
| 20 % | 76.4 % |
| 30 % | 64.5 % |
| 50 % | 40.9 % |
| 85 % | 0.0 % |
Enlarge chart
Scroll the full chart horizontally and vertically.
Exact values, units and download
| allowed_south_increase_pct | required_north_elsewhere_pct | north_reference_vehicles_day | south_reference_vehicles_day | status | source |
|---|---|---|---|---|---|
| 0 | 100.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 1 | 98.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 2 | 97.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 3 | 96.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 4 | 95.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 5 | 94.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 6 | 92.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 7 | 91.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 8 | 90.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 9 | 89.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 10 | 88.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 11 | 87.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 12 | 85.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 13 | 84.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 14 | 83.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 15 | 82.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 16 | 81.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 17 | 79.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 18 | 78.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 19 | 77.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 20 | 76.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 21 | 75.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 22 | 74.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 23 | 72.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 24 | 71.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 25 | 70.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 26 | 69.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 27 | 68.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 28 | 66.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 29 | 65.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 30 | 64.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 31 | 63.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 32 | 62.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 33 | 61.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 34 | 59.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 35 | 58.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 36 | 57.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 37 | 56.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 38 | 55.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 39 | 53.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 40 | 52.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 41 | 51.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 42 | 50.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 43 | 49.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 44 | 48.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 45 | 46.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 46 | 45.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 47 | 44.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 48 | 43.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 49 | 42.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 50 | 40.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 51 | 39.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 52 | 38.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 53 | 37.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 54 | 36.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 55 | 35.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 56 | 33.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 57 | 32.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 58 | 31.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 59 | 30.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 60 | 29.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 61 | 27.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 62 | 26.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 63 | 25.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 64 | 24.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 65 | 23.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 66 | 22.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 67 | 20.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 68 | 19.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 69 | 18.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 70 | 17.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 71 | 16.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 72 | 14.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 73 | 13.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 74 | 12.54545455 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 75 | 11.36363636 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 76 | 10.18181818 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 77 | 9.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 78 | 7.81818182 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 79 | 6.63636364 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 80 | 5.45454545 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 81 | 4.27272727 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 82 | 3.09090909 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 83 | 1.90909091 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 84 | 0.72727273 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
| 85 | 0.00000000 | 55000 | 65000 | scenario accounting; no capacity estimate | S08;own calculation |
Moving a journey from 8 a.m. to 10 a.m. on the same bridge would not reduce its daily total. It might help the peak considerably, but that is a different mechanism. The distinction is deliberately preserved in the interactive exercise. Otherwise, an apparently simple diversion assumption would quietly combine changes in daily demand with changes in its timing.
Access belongs to households and firms on both banks
The official Länder commuter accounts record 28,845 potential commuters between Mannheim and Ludwigshafen in 2024. Of these, 17,641 lived in Ludwigshafen and worked in Mannheim; 11,204 made the opposite residential-workplace connection. These are recorded employment relationships between places, which should not be converted into daily vehicle counts without information on attendance, mode choice and occupancy. Official 2024 commuter flows
The appropriate denominator changes the interpretation. Adding internal and outbound commuters gives 88,684 recorded employed residents in Ludwigshafen. Mannheim is the workplace of 19.9 percent of them. In the opposite direction, Ludwigshafen accounts for 6.5 percent of Mannheim's 172,289 recorded employed residents. Restricting the denominator to outbound commuters produces shares of 38.8 and 16.2 percent, respectively. The first comparison describes dependence across the recorded resident workforce; the second describes the concentration of external workplaces. Rhineland-Palatinate denominators, Baden-Württemberg denominators
One labor market, unequal dependence
Recorded person relationships, not observed daily trips.
Show compact values
| Home → work | Employed¹ | Outbound² |
|---|---|---|
| LU → MA | 19.9% | 38.8% |
| MA → LU | 6.5% | 16.2% |
Enlarge chart
Scroll the full chart horizontally and vertically.
Exact values, units and download
| origin | destination | denominator_label | commuters | denominator | share_pct | source |
|---|---|---|---|---|---|---|
| Mannheim | Ludwigshafen | alle erfassten Erwerbstätigen am Wohnort | 11204 | 172289 | 6.50302689 | S03-2024;S04-08 |
| Mannheim | Ludwigshafen | nur Auspendelnde | 11204 | 69243 | 16.18069697 | S03-2024;S04-08 |
| Ludwigshafen | Mannheim | alle erfassten Erwerbstätigen am Wohnort | 17641 | 88684 | 19.89197600 | S03-2024;S04-07 |
| Ludwigshafen | Mannheim | nur Auspendelnde | 17641 | 45502 | 38.76972441 | S03-2024;S04-07 |
The asymmetry does not establish that one municipality bears a correspondingly larger economic loss. The household encountering a longer journey may be in Ludwigshafen, while the employer having difficulty staffing a shift is in Mannheim. Because the relationship has two ends, each jurisdiction's administrative boundary cuts through the economic benefit of making it work.
This is one reason the value of a crossing is difficult to locate in a single budget. A transport improvement can expand the set of jobs a household can realistically consider and the set of workers a firm can reach. The present data do not estimate that expansion, but they identify a substantial set of existing relationships for which reliable access already matters.
Those relationships were also becoming more numerous before the current closure. Between 2021 and 2024, the combined count rose by 1,293, or 4.7 percent. Ludwigshafen-to-Mannheim relationships increased by 1,361; the opposite direction declined by 68. The first direction thus grew by 8.4 percent, while the second was broadly stable, ending 0.6 percent below its 2021 level.
The growing connection starts in Ludwigshafen
The trend predates the closure and is not a closure effect.
Show compact values
| Year | LU → MA | MA → LU |
|---|---|---|
| 2021 | 16,280 | 11,272 |
| 2022 | 16,574 | 11,666 |
| 2023 | 17,141 | 11,432 |
| 2024 | 17,641 | 11,204 |
Enlarge chart
Scroll the full chart horizontally and vertically.
Exact values, units and download
| year | origin | destination | commuters | source | unit | source_field | index_2021_100 |
|---|---|---|---|---|---|---|---|
| 2021 | Mannheim | Ludwigshafen | 11272 | S03-2021 | potenziell Pendelnde | AUSP_AO | 100.00000000 |
| 2021 | Ludwigshafen | Mannheim | 16280 | S03-2021 | potenziell Pendelnde | EIP_WO | 100.00000000 |
| 2022 | Mannheim | Ludwigshafen | 11666 | S03-2022 | potenziell Pendelnde | AUSP_AO | 103.49538680 |
| 2022 | Ludwigshafen | Mannheim | 16574 | S03-2022 | potenziell Pendelnde | EIP_WO | 101.80589681 |
| 2023 | Mannheim | Ludwigshafen | 11432 | S03-2023 | potenziell Pendelnde | AUSP_AO | 101.41944642 |
| 2023 | Ludwigshafen | Mannheim | 17141 | S03-2023 | potenziell Pendelnde | EIP_WO | 105.28869779 |
| 2024 | Mannheim | Ludwigshafen | 11204 | S03-2024 | potenziell Pendelnde | AUSP_AO | 99.39673527 |
| 2024 | Ludwigshafen | Mannheim | 17641 | S03-2024 | potenziell Pendelnde | EIP_WO | 108.35995086 |
The trend predates the closure, so it cannot be attributed to a 2026 event. Since the source files contain only the ten leading destinations or origins for each municipality, an absent edge cannot be interpreted as zero. The study therefore uses the directly published city-pair relationship rather than summing the visible edges into a purportedly complete regional labor market. 2021 commuter file, 2022, 2023, 2024
A border is a poor substitute for a journey
The earlier version of this research asked whether the Rhine acted as an invisible border tax. Geography and administration coincide here, making a separate state-border effect difficult to identify. A strong version of the claim would also have to survive inconvenient comparisons.
One such comparison comes from the archived timetable analysis. Starting at Mannheim's main station, the stored connections were used to calculate the earliest available arrival for each of 180 possible start minutes between 6:30 and 9:29 a.m. on September 16. The archived feed was dated August 24, 2026. Waiting counts as part of elapsed time.
In that calculation, the median scheduled elapsed time to Ludwigshafen Mitte was nine minutes. To Mannheim Marktplatz it was eleven. Ludwigshafen Mitte could be reached within twelve minutes for 164 of the 180 possible starting minutes, or 91.1 percent. Crossing the river was competitive with a journey remaining inside Mannheim. Archived routing evidence and reproducible calculation
A scheduled journey across the river can be quicker
Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.
Show compact values
| Budget | LU Mitte | MA Marktplatz |
|---|---|---|
| 5 min | 10.0 % | 0.0 % |
| 9 min | 56.1 % | 10.0 % |
| 10 min | 67.2 % | 30.0 % |
| 11 min | 81.7 % | 65.0 % |
| 12 min | 91.1 % | 80.0 % |
| 15 min | 100.0 % | 100.0 % |
Enlarge chart
Scroll the full chart horizontally and vertically.
Ludwigshafen Mitte: 91,1 % (164/180)
Mannheim Marktplatz:
Exact values, units and download
| destination | budget_min | start_minutes_within | total_start_minutes | share_pct | source | status |
|---|---|---|---|---|---|---|
| Ludwigshafen Mitte | 0 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 1 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 2 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 3 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 4 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 5 | 18 | 180 | 10.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 6 | 37 | 180 | 20.55555556 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 7 | 58 | 180 | 32.22222222 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 8 | 80 | 180 | 44.44444444 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 9 | 101 | 180 | 56.11111111 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 10 | 121 | 180 | 67.22222222 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 11 | 147 | 180 | 81.66666667 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 12 | 164 | 180 | 91.11111111 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 13 | 174 | 180 | 96.66666667 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 14 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 15 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 16 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 17 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 18 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 19 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 20 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Ludwigshafen Mitte | 21 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 0 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 1 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 2 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 3 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 4 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 5 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 6 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 7 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 8 | 0 | 180 | 0.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 9 | 18 | 180 | 10.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 10 | 54 | 180 | 30.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 11 | 117 | 180 | 65.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 12 | 144 | 180 | 80.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 13 | 162 | 180 | 90.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 14 | 171 | 180 | 95.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 15 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 16 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 17 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 18 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 19 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 20 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
| Mannheim Marktplatz | 21 | 180 | 180 | 100.00000000 | S07 | archivierter Sollfahrplan |
The result is deliberately retained as an archival finding because a fresh query of the original routing service was unavailable during the update; it cannot therefore serve as a currently verified travel recommendation. It includes neither real-time delays nor journeys from an arbitrary home to the main station or from Ludwigshafen Mitte to an arbitrary workplace.
The limitation points toward the useful unit of analysis: the complete journey at the required time. A direct rail connection may be an excellent substitute when the endpoints align with it, while offering little help to someone whose shift starts before the feeder service operates. Distance to a station, transfer reliability, access at the destination and the ability to change working hours determine how usable the nominal alternative is.
The historical road evidence is similarly specific. An INOVAPLAN accessibility study queried Google Maps travel-time estimates at fifteen-minute intervals over two weeks in January 2020. On its short Konrad Adenauer Bridge section toward Ludwigshafen, 26 percent of queries exceeded that section's own mean time by more than 30 percent. The two Kurt Schumacher sections recorded 11 and 9 percent; the southern section toward Mannheim recorded 1 percent. MRN/IHK/INOVAPLAN 2020, Table 14
The southern alternative had historical weak spots
Short sections of different lengths; historical queries, not current congestion rates.
Show compact values
| Bridge section → destination | Share > 130% of own mean |
|---|---|
| Konrad-Adenauer → Ludwigshafen | 26 % |
| Kurt-Schumacher → Ludwigshafen | 11 % |
| Kurt-Schumacher → Mannheim | 9 % |
| Konrad-Adenauer → Mannheim | 1 % |
Enlarge chart
Scroll the full chart horizontally and vertically.
Exact values, units and download
| bridge | direction | min_seconds | mean_seconds | max_seconds | share_above_1_3_mean_pct | length_km | source | period |
|---|---|---|---|---|---|---|---|---|
| Konrad-Adenauer | Ludwigshafen | 23 | 70 | 282 | 26 | 0.31300000 | S06 | 2020-01-11/2020-01-24 |
| Kurt-Schumacher | Ludwigshafen | 41 | 52 | 160 | 11 | 0.72400000 | S06 | 2020-01-11/2020-01-24 |
| Kurt-Schumacher | Mannheim | 38 | 49 | 133 | 9 | 0.75700000 | S06 | 2020-01-11/2020-01-24 |
| Konrad-Adenauer | Mannheim | 22 | 27 | 361 | 1 | 0.38700000 | S06 | 2020-01-11/2020-01-24 |
These are old estimates for short sections of different lengths, each compared with its own mean. They are not current congestion rates or observations of independent travelers. The same report's regional comparison also placed the morning premium relative to the best travel time at 18 percent for cross-Rhine routes and 25 percent for routes within Baden-Württemberg. The route sets differ, so this does not establish a causal advantage of crossing the river. It does rule out treating the river as a sufficient explanation of every difficult journey.
Less traffic can mean several things
Observed traffic is an outcome of both the opportunities available and the choices people make in response. After a closure, a lower count at a particular location could reflect successful mode substitution. It could also reflect longer detours, fewer visits, postponed appointments or working arrangements that people would not otherwise have chosen.
For that reason, the absence of a visible queue cannot by itself establish the absence of a cost. Equally, displaced vehicle passages cannot simply be multiplied by an assumed delay and called a measured welfare loss. Some journeys may improve, some may disappear at little cost, and others may impose substantial inconvenience. The distribution of changes matters alongside their average.
A useful monitoring design would therefore combine direction-specific traffic and travel times with public-transport arrival reliability, active-travel counts and repeated surveys of complete work journeys. The network's construction state should be recorded alongside holidays, weather and major incidents. Comparisons need consistent weekdays and time windows. A control route affected by the same diversion is not an unaffected control simply because it does not cross the closed bridge.
The objective is not to prescribe an elaborate model before knowing what data exist. It is to make a subsequent estimate answer a defined question. A model of peak road delay, a measure of access to jobs and an estimate of household time costs are different objects. They should not acquire the same label merely because they concern the same closure.
A transparent scale calculation
Consider 10,000 affected person-trips per day, each taking ten additional minutes. Together they generate roughly 1,667 additional person-hours daily. At an assumed €20 per person-hour over 250 assumed days, the annualized time value is approximately €8.3 million.
How additional minutes accumulate
All inputs are assumptions. Not a measured closure cost or a GDP loss.
Show compact values
| Person-trips/day | 5 min | 10 min | 15 min | 20 min |
|---|---|---|---|---|
| 5,000 | 2.1 | 4.2 | 6.2 | 8.3 |
| 10,000 | 4.2 | 8.3 | 12.5 | 16.7 |
| 15,000 | 6.2 | 12.5 | 18.8 | 25.0 |
| 20,000 | 8.3 | 16.7 | 25.0 | 33.3 |
| 25,000 | 10.4 | 20.8 | 31.2 | 41.7 |
Enlarge chart
Scroll the full chart horizontally and vertically.
All inputs are assumptions. Not a measured closure cost or a GDP loss.
Exact values, units and download
| affected_person_trips_day | additional_minutes | assumed_days | assumed_eur_person_hour | hours_day | annual_time_value_eur | status |
|---|---|---|---|---|---|---|
| 5000 | 5 | 250 | 20 | 416.66666667 | 2083333.33333333 | hypothetical scenario; not a measured closure cost |
| 5000 | 10 | 250 | 20 | 833.33333333 | 4166666.66666667 | hypothetical scenario; not a measured closure cost |
| 5000 | 15 | 250 | 20 | 1250.00000000 | 6250000.00000000 | hypothetical scenario; not a measured closure cost |
| 5000 | 20 | 250 | 20 | 1666.66666667 | 8333333.33333333 | hypothetical scenario; not a measured closure cost |
| 10000 | 5 | 250 | 20 | 833.33333333 | 4166666.66666667 | hypothetical scenario; not a measured closure cost |
| 10000 | 10 | 250 | 20 | 1666.66666667 | 8333333.33333333 | hypothetical scenario; not a measured closure cost |
| 10000 | 15 | 250 | 20 | 2500.00000000 | 12500000.00000000 | hypothetical scenario; not a measured closure cost |
| 10000 | 20 | 250 | 20 | 3333.33333333 | 16666666.66666667 | hypothetical scenario; not a measured closure cost |
| 15000 | 5 | 250 | 20 | 1250.00000000 | 6250000.00000000 | hypothetical scenario; not a measured closure cost |
| 15000 | 10 | 250 | 20 | 2500.00000000 | 12500000.00000000 | hypothetical scenario; not a measured closure cost |
| 15000 | 15 | 250 | 20 | 3750.00000000 | 18750000.00000000 | hypothetical scenario; not a measured closure cost |
| 15000 | 20 | 250 | 20 | 5000.00000000 | 25000000.00000000 | hypothetical scenario; not a measured closure cost |
| 20000 | 5 | 250 | 20 | 1666.66666667 | 8333333.33333333 | hypothetical scenario; not a measured closure cost |
| 20000 | 10 | 250 | 20 | 3333.33333333 | 16666666.66666667 | hypothetical scenario; not a measured closure cost |
| 20000 | 15 | 250 | 20 | 5000.00000000 | 25000000.00000000 | hypothetical scenario; not a measured closure cost |
| 20000 | 20 | 250 | 20 | 6666.66666667 | 33333333.33333334 | hypothetical scenario; not a measured closure cost |
| 25000 | 5 | 250 | 20 | 2083.33333333 | 10416666.66666667 | hypothetical scenario; not a measured closure cost |
| 25000 | 10 | 250 | 20 | 4166.66666667 | 20833333.33333334 | hypothetical scenario; not a measured closure cost |
| 25000 | 15 | 250 | 20 | 6250.00000000 | 31250000.00000000 | hypothetical scenario; not a measured closure cost |
| 25000 | 20 | 250 | 20 | 8333.33333333 | 41666666.66666667 | hypothetical scenario; not a measured closure cost |
Every input in the example is an assumption, with the 10,000 person-trips specified independently of the 55,000 vehicle passages. A return journey counts twice if both legs incur the stated delay, while the illustrative €20 hourly value and 250 days define how the resulting time is valued. The sensitivity table displays exact outcomes under alternative assumptions; it is not a confidence interval around an estimated closure cost.
The example provides a way to ask whether accelerating a safe repair or improving a replacement connection could be worth its cost. Under the stated assumptions, one-twelfth of the modeled duration corresponds to about €0.7 million in gross time value. A real proposal would have to establish how much of the assumed burden it actually removes, for how long, and at what implementation cost.
Other effects remain outside this arithmetic. Unreliable travel may require additional buffers, while missed connections or inflexible schedules may constrain the feasible alternatives. Conversely, an hour of personal time saved does not automatically become an hour of paid production. Time value is not interchangeable with lost GDP, and a scenario total should not acquire that interpretation as it moves into a headline.
What the second crossing was providing
The case establishes substantial integration, asymmetric dependence and a demanding arithmetic of diversion. It also establishes the limits of a broad border narrative. Some cross-river journeys have useful rail alternatives, and historical road performance varied sharply by section and direction.
What remains unmeasured here is the realized distribution of delay, adaptation and lost access since the closure, and that gap should determine the next measurement effort. A more confident adjective would do little to resolve it.
For infrastructure policy, the broader implication is that an alternative connection can have value even when another route remains open. Its contribution depends on whether it provides a workable substitute when the network changes. This makes redundancy an economic question about access, reliability and the range of feasible choices, as well as an engineering question about structures.
The Rhine still separates two municipalities and two states. Whether it separates their labor markets more strongly now depends on the journeys people can actually complete. A successful response to the closure would preserve those possibilities, especially for people whose working lives leave them little room to improvise.
Methods and source boundaries
The commuter calculations use the official 2021–2024 state flow files and 2024 municipal totals. Employed residents are represented by internal plus outbound potential commuters. Published top-ten relationships are not a complete origin-destination matrix. Historical road indicators come from Tables 2, 13 and 14 of the 2020 MRN/IHK/INOVAPLAN study. Archived timetable itineraries are retained with their feed date, query URLs, scheduled status and recomputed start-minute results. They are not real-time observations or a newly verified September 4 timetable.
Traffic accounting uses N = 55,000 and S = 65,000 reference vehicle passages per day. If a is the share of former northern passages accommodated outside the southern daily total, the scenario gives S′ = S + N(1 − a). A chosen proportional southern increase g requires a ≥ max(0, 1 − gS/N). Neither expression estimates capacity or congestion. Time value is Q × d / 60 × D × v, where Q is affected person-trips per day, d is additional minutes per trip, D is assumed days and v is euros per person-hour. All inputs remain independently adjustable. The evidence package includes exact values, sources, acquisition receipts, calculations and validation records.