SCHYM.DE · RESEARCHMethods & data
Mannheim × Ludwigshafen · September 4, 2026

The Value of a Second Way Across

A closed Rhine bridge reveals what traffic counts miss about the economics of alternatives

Michael Schymura · Structural evidence and transparent scenarios

June 1: tram closed · August 5: road closed · August 31: new southern access ramp
28,845recorded commuting relationships between the cities, 2024. Not counted daily trips.

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.

Exhibit 01 · Status

Several ways across, one road link missing

Lines show connections; width does not encode capacity.

SCHYM / RHEIN–NECKAR01 / 08Several ways across, one road link missingSchematic crossings · status on September 4, 2026 · not a navigation mapCity of Mannheim, July 30; Ludwigshafen construction updates; rnv.Lines show connections; width does not encode capacity.RHEINLUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing availableSCHYM / RHEIN–NECKAR01 / 08Several ways across, one road link missingSchematic crossings · status on September 4, 2026 · not a navigation mapCity of Mannheim, July 30; Ludwigshafen construction updates; rnv.Lines show connections; width does not encode capacity.RHEINLUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing available
LUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing availableRHEINSchematic · no capacity scaleLUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing availableRHEINSchematic · no capacity scale
Show compact values
Schematic crossings · status on September 4, 2026 · not a navigation map
ConnectionStatus
A6 / Theodor HeussRoad · diversion
Kurt SchumacherRoad + tram · closed
Kurt SchumacherWalk + cycle · open
Konrad AdenauerRoad · alternative
Rail corridorCrossing available
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR01 / 08Several ways across, one road link missingSchematic crossings · status on September 4, 2026 · not a navigation mapCity of Mannheim, July 30; Ludwigshafen construction updates; rnv.Lines show connections; width does not encode capacity.RHEINLUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing availableSCHYM / RHEIN–NECKAR01 / 08Several ways across, one road link missingSchematic crossings · status on September 4, 2026 · not a navigation mapCity of Mannheim, July 30; Ludwigshafen construction updates; rnv.Lines show connections; width does not encode capacity.RHEINLUDWIGSHAFENMANNHEIMA6 / Theodor HeussRoad diversionKurt SchumacherRoad + tram closedKurt SchumacherWalking + cycling openKonrad AdenauerRoad alternativeRail corridorRail crossing available
Source: Mannheim · 30.07.2026 · Ludwigshafen · Baustellenblog City of Mannheim, July 30; Ludwigshafen construction updates; rnv.
Exact values, units and download
linkmodestatussincesource
Kurt-Schumacher-BrückeKfzgesperrt2026-08-05S01
Kurt-Schumacher-BrückeStraßenbahngesperrt2026-06-01S01
Kurt-Schumacher-BrückeFuß / Radoffen2026-08-05S01
Konrad-Adenauer-KorridorKfzAusweichquerung; Zufahrten teils eingeschränkt2026-09-04S01;S02
Konrad-Adenauer-KorridorSchieneRheinquerung bleibt möglich2026-09-04S01;S05
A6 / Theodor-Heuss-BrückeKfzgroßräumige Umleitung2026-08-05S01

Download values as CSV

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.

Exhibit 02 · Scenario

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.

SCHYM / RHEIN–NECKAR02 / 08Half the northern flow means 42% more in the southScenario using rounded daily reference vehicle passages · not a forecastSWR / Mannheim administration: north ≈ 55,000, combined ≈ 120,000; south derived ≈ 65,000.“Elsewhere”: other routes, modes or foregone trips; not simply a change of time on the same day.NORTH · reference55,000SOUTH65,000Elsewhere27,500SOUTH92,500+42%Additional 27,500SCHYM / RHEIN–NECKAR02 / 08Half the northern flow means 42% more in the southScenario using rounded daily reference vehicle passages · not a forecastSWR / Mannheim administration: north ≈ 55,000, combined ≈ 120,000; south derived ≈ 65,000.“Elsewhere”: other routes, modes or foregone trips; not simply a change of time on the same day.NORTH · reference55,000SOUTH65,000Elsewhere27,500SOUTH92,500+42%Additional 27,500
Scenario · vehicle passages per dayNORTH55,000SOUTH65,000+27,500Elsewhere27,500SOUTH IN SCENARIO92,500+42.3%Proportional bands · total remains 120,000Scenario · vehicle passages per dayNORTH55,000SOUTH65,000+27,500Elsewhere27,500SOUTH IN SCENARIO92,500+42.3%Proportional bands · total remains 120,000
Show compact values
Scenario using rounded daily reference vehicle passages · not a forecast
Scenario · 50% elsewhereVehicles/day
Southern reference65,000
Additional from north27,500
Southern scenario total92,500
Accommodated elsewhere27,500
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR02 / 08Half the northern flow means 42% more in the southScenario using rounded daily reference vehicle passages · not a forecastSWR / Mannheim administration: north ≈ 55,000, combined ≈ 120,000; south derived ≈ 65,000.“Elsewhere”: other routes, modes or foregone trips; not simply a change of time on the same day.NORTH · reference55,000SOUTH65,000Elsewhere27,500SOUTH92,500+42%Additional 27,500SCHYM / RHEIN–NECKAR02 / 08Half the northern flow means 42% more in the southScenario using rounded daily reference vehicle passages · not a forecastSWR / Mannheim administration: north ≈ 55,000, combined ≈ 120,000; south derived ≈ 65,000.“Elsewhere”: other routes, modes or foregone trips; not simply a change of time on the same day.NORTH · reference55,000SOUTH65,000Elsewhere27,500SOUTH92,500+42%Additional 27,500
Other routes, modes or foregone trips. Moving only the time on the same day is not included.
92.500Vehicle passages in southern scenario / day
+42,3 %relative to the southern reference
Southern reference: 65,000Additional: 27.500

Elsewhere: 27.500 · Both bars: 0–120,000 vehicles/day.

Source: SWR / Mannheim SWR / Mannheim administration: north ≈ 55,000, combined ≈ 120,000; south derived ≈ 65,000.
Exact values, units and download
origindestinationvehicles_daystatus
Nordkorridor: frühere FahrtenSüdkorridor: angenommene Zusatzmenge27500.00000000scenario
Nordkorridor: frühere Fahrtenandere Route / Verkehrsmittel / entfallene Fahrt27500.00000000scenario
Südkorridor: ReferenzSüdkorridor: bisherige Menge65000.00000000reference-derived

Download values as CSV

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.

Exhibit 03 · Scenario

A diversion target has an arithmetic cost

The increase is a chosen condition, not an observed capacity limit.

SCHYM / RHEIN–NECKAR03 / 08A diversion target has an arithmetic costFormer northern passages that must stay outside the southern daily totalOwn calculation; reference north 55,000 and south 65,000 vehicle passages per day.The increase is a chosen condition, not an observed capacity limit.0 %25 %50 %75 %100 %0 %20 %40 %60 %80 %Chosen increase in southern daily traffic30% → 64.5%Required elsewhereSCHYM / RHEIN–NECKAR03 / 08A diversion target has an arithmetic costFormer northern passages that must stay outside the southern daily totalOwn calculation; reference north 55,000 and south 65,000 vehicle passages per day.The increase is a chosen condition, not an observed capacity limit.0 %25 %50 %75 %100 %0 %20 %40 %60 %80 %Chosen increase in southern daily traffic30% → 64.5%Required elsewhere
Required adjustment elsewhere (%)0255075100020406080Chosen southern increase (%)30% in the south → 64.5% elsewhereChosen condition, not a capacity limitRequired adjustment elsewhere (%)0255075100020406080Chosen southern increase (%)30% in the south → 64.5% elsewhereChosen condition, not a capacity limit
Show compact values
Former northern passages that must stay outside the southern daily total
Southern increaseRequired 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.

SCHYM / RHEIN–NECKAR03 / 08A diversion target has an arithmetic costFormer northern passages that must stay outside the southern daily totalOwn calculation; reference north 55,000 and south 65,000 vehicle passages per day.The increase is a chosen condition, not an observed capacity limit.0 %25 %50 %75 %100 %0 %20 %40 %60 %80 %Chosen increase in southern daily traffic30% → 64.5%Required elsewhereSCHYM / RHEIN–NECKAR03 / 08A diversion target has an arithmetic costFormer northern passages that must stay outside the southern daily totalOwn calculation; reference north 55,000 and south 65,000 vehicle passages per day.The increase is a chosen condition, not an observed capacity limit.0 %25 %50 %75 %100 %0 %20 %40 %60 %80 %Chosen increase in southern daily traffic30% → 64.5%Required elsewhere
The increase is a chosen condition, not an observed capacity limit.

Source: SWR / Mannheim Own calculation; reference north 55,000 and south 65,000 vehicle passages per day.
Exact values, units and download
allowed_south_increase_pctrequired_north_elsewhere_pctnorth_reference_vehicles_daysouth_reference_vehicles_daystatussource
0100.000000005500065000scenario accounting; no capacity estimateS08;own calculation
198.818181825500065000scenario accounting; no capacity estimateS08;own calculation
297.636363645500065000scenario accounting; no capacity estimateS08;own calculation
396.454545455500065000scenario accounting; no capacity estimateS08;own calculation
495.272727275500065000scenario accounting; no capacity estimateS08;own calculation
594.090909095500065000scenario accounting; no capacity estimateS08;own calculation
692.909090915500065000scenario accounting; no capacity estimateS08;own calculation
791.727272735500065000scenario accounting; no capacity estimateS08;own calculation
890.545454555500065000scenario accounting; no capacity estimateS08;own calculation
989.363636365500065000scenario accounting; no capacity estimateS08;own calculation
1088.181818185500065000scenario accounting; no capacity estimateS08;own calculation
1187.000000005500065000scenario accounting; no capacity estimateS08;own calculation
1285.818181825500065000scenario accounting; no capacity estimateS08;own calculation
1384.636363645500065000scenario accounting; no capacity estimateS08;own calculation
1483.454545455500065000scenario accounting; no capacity estimateS08;own calculation
1582.272727275500065000scenario accounting; no capacity estimateS08;own calculation
1681.090909095500065000scenario accounting; no capacity estimateS08;own calculation
1779.909090915500065000scenario accounting; no capacity estimateS08;own calculation
1878.727272735500065000scenario accounting; no capacity estimateS08;own calculation
1977.545454555500065000scenario accounting; no capacity estimateS08;own calculation
2076.363636365500065000scenario accounting; no capacity estimateS08;own calculation
2175.181818185500065000scenario accounting; no capacity estimateS08;own calculation
2274.000000005500065000scenario accounting; no capacity estimateS08;own calculation
2372.818181825500065000scenario accounting; no capacity estimateS08;own calculation
2471.636363645500065000scenario accounting; no capacity estimateS08;own calculation
2570.454545455500065000scenario accounting; no capacity estimateS08;own calculation
2669.272727275500065000scenario accounting; no capacity estimateS08;own calculation
2768.090909095500065000scenario accounting; no capacity estimateS08;own calculation
2866.909090915500065000scenario accounting; no capacity estimateS08;own calculation
2965.727272735500065000scenario accounting; no capacity estimateS08;own calculation
3064.545454555500065000scenario accounting; no capacity estimateS08;own calculation
3163.363636365500065000scenario accounting; no capacity estimateS08;own calculation
3262.181818185500065000scenario accounting; no capacity estimateS08;own calculation
3361.000000005500065000scenario accounting; no capacity estimateS08;own calculation
3459.818181825500065000scenario accounting; no capacity estimateS08;own calculation
3558.636363645500065000scenario accounting; no capacity estimateS08;own calculation
3657.454545455500065000scenario accounting; no capacity estimateS08;own calculation
3756.272727275500065000scenario accounting; no capacity estimateS08;own calculation
3855.090909095500065000scenario accounting; no capacity estimateS08;own calculation
3953.909090915500065000scenario accounting; no capacity estimateS08;own calculation
4052.727272735500065000scenario accounting; no capacity estimateS08;own calculation
4151.545454555500065000scenario accounting; no capacity estimateS08;own calculation
4250.363636365500065000scenario accounting; no capacity estimateS08;own calculation
4349.181818185500065000scenario accounting; no capacity estimateS08;own calculation
4448.000000005500065000scenario accounting; no capacity estimateS08;own calculation
4546.818181825500065000scenario accounting; no capacity estimateS08;own calculation
4645.636363645500065000scenario accounting; no capacity estimateS08;own calculation
4744.454545455500065000scenario accounting; no capacity estimateS08;own calculation
4843.272727275500065000scenario accounting; no capacity estimateS08;own calculation
4942.090909095500065000scenario accounting; no capacity estimateS08;own calculation
5040.909090915500065000scenario accounting; no capacity estimateS08;own calculation
5139.727272735500065000scenario accounting; no capacity estimateS08;own calculation
5238.545454555500065000scenario accounting; no capacity estimateS08;own calculation
5337.363636365500065000scenario accounting; no capacity estimateS08;own calculation
5436.181818185500065000scenario accounting; no capacity estimateS08;own calculation
5535.000000005500065000scenario accounting; no capacity estimateS08;own calculation
5633.818181825500065000scenario accounting; no capacity estimateS08;own calculation
5732.636363645500065000scenario accounting; no capacity estimateS08;own calculation
5831.454545455500065000scenario accounting; no capacity estimateS08;own calculation
5930.272727275500065000scenario accounting; no capacity estimateS08;own calculation
6029.090909095500065000scenario accounting; no capacity estimateS08;own calculation
6127.909090915500065000scenario accounting; no capacity estimateS08;own calculation
6226.727272735500065000scenario accounting; no capacity estimateS08;own calculation
6325.545454555500065000scenario accounting; no capacity estimateS08;own calculation
6424.363636365500065000scenario accounting; no capacity estimateS08;own calculation
6523.181818185500065000scenario accounting; no capacity estimateS08;own calculation
6622.000000005500065000scenario accounting; no capacity estimateS08;own calculation
6720.818181825500065000scenario accounting; no capacity estimateS08;own calculation
6819.636363645500065000scenario accounting; no capacity estimateS08;own calculation
6918.454545455500065000scenario accounting; no capacity estimateS08;own calculation
7017.272727275500065000scenario accounting; no capacity estimateS08;own calculation
7116.090909095500065000scenario accounting; no capacity estimateS08;own calculation
7214.909090915500065000scenario accounting; no capacity estimateS08;own calculation
7313.727272735500065000scenario accounting; no capacity estimateS08;own calculation
7412.545454555500065000scenario accounting; no capacity estimateS08;own calculation
7511.363636365500065000scenario accounting; no capacity estimateS08;own calculation
7610.181818185500065000scenario accounting; no capacity estimateS08;own calculation
779.000000005500065000scenario accounting; no capacity estimateS08;own calculation
787.818181825500065000scenario accounting; no capacity estimateS08;own calculation
796.636363645500065000scenario accounting; no capacity estimateS08;own calculation
805.454545455500065000scenario accounting; no capacity estimateS08;own calculation
814.272727275500065000scenario accounting; no capacity estimateS08;own calculation
823.090909095500065000scenario accounting; no capacity estimateS08;own calculation
831.909090915500065000scenario accounting; no capacity estimateS08;own calculation
840.727272735500065000scenario accounting; no capacity estimateS08;own calculation
850.000000005500065000scenario accounting; no capacity estimateS08;own calculation

Download values as CSV

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

Exhibit 04 · Official data

One labor market, unequal dependence

Recorded person relationships, not observed daily trips.

SCHYM / RHEIN–NECKAR04 / 08One labor market, unequal dependenceShare working in the neighboring city · official commuter accounts, 2024Official commuter accounts 2024; denominator = internal + outbound, or outbound only.Recorded person relationships, not observed daily trips.All recorded employed residentsShare working across the river0 %10 %20 %30 %40 %Outbound commuters onlyShare working across the river0 %10 %20 %30 %40 %LU → MA 19.9 %MA → LU 6.5 %LU → MA 38.8 %MA → LU 16.2 %SCHYM / RHEIN–NECKAR04 / 08One labor market, unequal dependenceShare working in the neighboring city · official commuter accounts, 2024Official commuter accounts 2024; denominator = internal + outbound, or outbound only.Recorded person relationships, not observed daily trips.All recorded employed residentsShare working across the river0 %10 %20 %30 %40 %Outbound commuters onlyShare working across the river0 %10 %20 %30 %40 %LU → MA 19.9 %MA → LU 6.5 %LU → MA 38.8 %MA → LU 16.2 %
All recorded employed residents0%10%20%30%40%LU → MA 19.9%MA → LU 6.5%Outbound commuters only0%10%20%30%40%LU → MA 38.8%MA → LU 16.2%Share working in the neighboring city · 2024All recorded employed residents0%10%20%30%40%LU → MA 19.9%MA → LU 6.5%Outbound commuters only0%10%20%30%40%LU → MA 38.8%MA → LU 16.2%Share working in the neighboring city · 2024
Show compact values
¹ All recorded employed residents. ² Outbound commuters only. Same numerator, different denominators.
Home → workEmployed¹Outbound²
LU → MA19.9%38.8%
MA → LU6.5%16.2%
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR04 / 08One labor market, unequal dependenceShare working in the neighboring city · official commuter accounts, 2024Official commuter accounts 2024; denominator = internal + outbound, or outbound only.Recorded person relationships, not observed daily trips.All recorded employed residentsShare working across the river0 %10 %20 %30 %40 %Outbound commuters onlyShare working across the river0 %10 %20 %30 %40 %LU → MA 19.9 %MA → LU 6.5 %LU → MA 38.8 %MA → LU 16.2 %SCHYM / RHEIN–NECKAR04 / 08One labor market, unequal dependenceShare working in the neighboring city · official commuter accounts, 2024Official commuter accounts 2024; denominator = internal + outbound, or outbound only.Recorded person relationships, not observed daily trips.All recorded employed residentsShare working across the river0 %10 %20 %30 %40 %Outbound commuters onlyShare working across the river0 %10 %20 %30 %40 %LU → MA 19.9 %MA → LU 6.5 %LU → MA 38.8 %MA → LU 16.2 %
Source: Pendlerrechnung 2024 · Rheinland-Pfalz · Baden-Württemberg Official commuter accounts 2024; denominator = internal + outbound, or outbound only.
Exact values, units and download
origindestinationdenominator_labelcommutersdenominatorshare_pctsource
MannheimLudwigshafenalle erfassten Erwerbstätigen am Wohnort112041722896.50302689S03-2024;S04-08
MannheimLudwigshafennur Auspendelnde112046924316.18069697S03-2024;S04-08
LudwigshafenMannheimalle erfassten Erwerbstätigen am Wohnort176418868419.89197600S03-2024;S04-07
LudwigshafenMannheimnur Auspendelnde176414550238.76972441S03-2024;S04-07

Download values as CSV

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.

Exhibit 05 · Official data

The growing connection starts in Ludwigshafen

The trend predates the closure and is not a closure effect.

SCHYM / RHEIN–NECKAR05 / 08The growing connection starts in LudwigshafenPotential commuting relationships · 2021 = 100 · annual official valuesCommuter accounts 2021–2024; top-ten files: missing relationships are not zero.The trend predates the closure and is not a closure effect.981001041081102021202220232024LU → MA17,641+8.4%MA → LU11,204−0.6%2021: LU → MA 16,280 · MA → LU 11,272SCHYM / RHEIN–NECKAR05 / 08The growing connection starts in LudwigshafenPotential commuting relationships · 2021 = 100 · annual official valuesCommuter accounts 2021–2024; top-ten files: missing relationships are not zero.The trend predates the closure and is not a closure effect.981001041081102021202220232024LU → MA17,641+8.4%MA → LU11,204−0.6%2021: LU → MA 16,280 · MA → LU 11,272
Commuting relationships · 2021 = 100LU → MAMA → LU981001041081102021202220232024LU → MA: 17,641 · +8.4%MA → LU: 11,204 · -0.6%Commuting relationships · 2021 = 100LU → MAMA → LU981001041081102021202220232024LU → MA: 17,641 · +8.4%MA → LU: 11,204 · -0.6%
Show compact values
Potential commuting relationships · 2021 = 100 · annual official values
YearLU → MAMA → LU
202116,28011,272
202216,57411,666
202317,14111,432
202417,64111,204
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR05 / 08The growing connection starts in LudwigshafenPotential commuting relationships · 2021 = 100 · annual official valuesCommuter accounts 2021–2024; top-ten files: missing relationships are not zero.The trend predates the closure and is not a closure effect.981001041081102021202220232024LU → MA17,641+8.4%MA → LU11,204−0.6%2021: LU → MA 16,280 · MA → LU 11,272SCHYM / RHEIN–NECKAR05 / 08The growing connection starts in LudwigshafenPotential commuting relationships · 2021 = 100 · annual official valuesCommuter accounts 2021–2024; top-ten files: missing relationships are not zero.The trend predates the closure and is not a closure effect.981001041081102021202220232024LU → MA17,641+8.4%MA → LU11,204−0.6%2021: LU → MA 16,280 · MA → LU 11,272
Source: Pendlerrechnung 2021–2024 Commuter accounts 2021–2024; top-ten files: missing relationships are not zero.
Exact values, units and download
yearorigindestinationcommuterssourceunitsource_fieldindex_2021_100
2021MannheimLudwigshafen11272S03-2021potenziell PendelndeAUSP_AO100.00000000
2021LudwigshafenMannheim16280S03-2021potenziell PendelndeEIP_WO100.00000000
2022MannheimLudwigshafen11666S03-2022potenziell PendelndeAUSP_AO103.49538680
2022LudwigshafenMannheim16574S03-2022potenziell PendelndeEIP_WO101.80589681
2023MannheimLudwigshafen11432S03-2023potenziell PendelndeAUSP_AO101.41944642
2023LudwigshafenMannheim17141S03-2023potenziell PendelndeEIP_WO105.28869779
2024MannheimLudwigshafen11204S03-2024potenziell PendelndeAUSP_AO99.39673527
2024LudwigshafenMannheim17641S03-2024potenziell PendelndeEIP_WO108.35995086

Download values as CSV

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

Exhibit 06 · Archived schedule

A scheduled journey across the river can be quicker

Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.

SCHYM / RHEIN–NECKAR06 / 08A scheduled journey across the river can be quickerFrom Mannheim Hbf · share of 180 start minutes within a time budgetArchived DELFI/Transitous feed, Aug. 24; target Sept. 16, 2026, 06:30–09:29 CEST.Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.0 %25 %50 %75 %100 %05101520Time budget in minutesLudwigshafen MitteMannheim Marktplatz12 min → 91.1%SCHYM / RHEIN–NECKAR06 / 08A scheduled journey across the river can be quickerFrom Mannheim Hbf · share of 180 start minutes within a time budgetArchived DELFI/Transitous feed, Aug. 24; target Sept. 16, 2026, 06:30–09:29 CEST.Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.0 %25 %50 %75 %100 %05101520Time budget in minutesLudwigshafen MitteMannheim Marktplatz12 min → 91.1%
Ludwigshafen MitteMannheim MarktplatzStart minutes within the budget0%25%50%75%100%05101520Time budget in minutes12 min: LU 91.1% · MA 80.0%Archived schedule, including waitingLudwigshafen MitteMannheim MarktplatzStart minutes within the budget0%25%50%75%100%05101520Time budget in minutes12 min: LU 91.1% · MA 80.0%Archived schedule, including waiting
Show compact values
From Mannheim Hbf · share of 180 start minutes within a time budget
BudgetLU MitteMA Marktplatz
5 min10.0 %0.0 %
9 min56.1 %10.0 %
10 min67.2 %30.0 %
11 min81.7 %65.0 %
12 min91.1 %80.0 %
15 min100.0 %100.0 %
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR06 / 08A scheduled journey across the river can be quickerFrom Mannheim Hbf · share of 180 start minutes within a time budgetArchived DELFI/Transitous feed, Aug. 24; target Sept. 16, 2026, 06:30–09:29 CEST.Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.0 %25 %50 %75 %100 %05101520Time budget in minutesLudwigshafen MitteMannheim Marktplatz12 min → 91.1%SCHYM / RHEIN–NECKAR06 / 08A scheduled journey across the river can be quickerFrom Mannheim Hbf · share of 180 start minutes within a time budgetArchived DELFI/Transitous feed, Aug. 24; target Sept. 16, 2026, 06:30–09:29 CEST.Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.0 %25 %50 %75 %100 %05101520Time budget in minutesLudwigshafen MitteMannheim Marktplatz12 min → 91.1%
Scheduled elapsed time including waiting; no real-time data or complete home-to-work journey.

Ludwigshafen Mitte: 91,1 % (164/180)

Mannheim Marktplatz:

Source: DELFI / Transitous Archived DELFI/Transitous feed, Aug. 24; target Sept. 16, 2026, 06:30–09:29 CEST.
Exact values, units and download
destinationbudget_minstart_minutes_withintotal_start_minutesshare_pctsourcestatus
Ludwigshafen Mitte001800.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte101800.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte201800.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte301800.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte401800.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte51818010.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte63718020.55555556S07archivierter Sollfahrplan
Ludwigshafen Mitte75818032.22222222S07archivierter Sollfahrplan
Ludwigshafen Mitte88018044.44444444S07archivierter Sollfahrplan
Ludwigshafen Mitte910118056.11111111S07archivierter Sollfahrplan
Ludwigshafen Mitte1012118067.22222222S07archivierter Sollfahrplan
Ludwigshafen Mitte1114718081.66666667S07archivierter Sollfahrplan
Ludwigshafen Mitte1216418091.11111111S07archivierter Sollfahrplan
Ludwigshafen Mitte1317418096.66666667S07archivierter Sollfahrplan
Ludwigshafen Mitte14180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte15180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte16180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte17180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte18180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte19180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte20180180100.00000000S07archivierter Sollfahrplan
Ludwigshafen Mitte21180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz001800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz101800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz201800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz301800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz401800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz501800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz601800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz701800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz801800.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz91818010.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz105418030.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz1111718065.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz1214418080.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz1316218090.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz1417118095.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz15180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz16180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz17180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz18180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz19180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz20180180100.00000000S07archivierter Sollfahrplan
Mannheim Marktplatz21180180100.00000000S07archivierter Sollfahrplan

Download values as CSV

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

Exhibit 07 · Historical data

The southern alternative had historical weak spots

Short sections of different lengths; historical queries, not current congestion rates.

SCHYM / RHEIN–NECKAR07 / 08The southern alternative had historical weak spotsQueries above 130% of each section’s own mean time · January 2020MRN / IHK / INOVAPLAN 2020, Table 14; Google Maps estimates, January 11–24.Short sections of different lengths; historical queries, not current congestion rates.0 %10 %20 %30 %Konrad-Adenauer→ Ludwigshafen26 %Kurt-Schumacher→ Ludwigshafen11 %Kurt-Schumacher→ Mannheim9 %Konrad-Adenauer→ Mannheim1 %SCHYM / RHEIN–NECKAR07 / 08The southern alternative had historical weak spotsQueries above 130% of each section’s own mean time · January 2020MRN / IHK / INOVAPLAN 2020, Table 14; Google Maps estimates, January 11–24.Short sections of different lengths; historical queries, not current congestion rates.0 %10 %20 %30 %Konrad-Adenauer→ Ludwigshafen26 %Kurt-Schumacher→ Ludwigshafen11 %Kurt-Schumacher→ Mannheim9 %Konrad-Adenauer→ Mannheim1 %
Queries above 130% of own mean timeKonrad-Adenauer → LU26%Kurt-Schumacher → LU11%Kurt-Schumacher → MA9%Konrad-Adenauer → MA1%0%10%20%30%January 2020 · not current congestionQueries above 130% of own mean timeKonrad-Adenauer → LU26%Kurt-Schumacher → LU11%Kurt-Schumacher → MA9%Konrad-Adenauer → MA1%0%10%20%30%January 2020 · not current congestion
Show compact values
Queries above 130% of each section’s own mean time · January 2020
Bridge section → destinationShare > 130% of own mean
Konrad-Adenauer → Ludwigshafen26 %
Kurt-Schumacher → Ludwigshafen11 %
Kurt-Schumacher → Mannheim9 %
Konrad-Adenauer → Mannheim1 %
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR07 / 08The southern alternative had historical weak spotsQueries above 130% of each section’s own mean time · January 2020MRN / IHK / INOVAPLAN 2020, Table 14; Google Maps estimates, January 11–24.Short sections of different lengths; historical queries, not current congestion rates.0 %10 %20 %30 %Konrad-Adenauer→ Ludwigshafen26 %Kurt-Schumacher→ Ludwigshafen11 %Kurt-Schumacher→ Mannheim9 %Konrad-Adenauer→ Mannheim1 %SCHYM / RHEIN–NECKAR07 / 08The southern alternative had historical weak spotsQueries above 130% of each section’s own mean time · January 2020MRN / IHK / INOVAPLAN 2020, Table 14; Google Maps estimates, January 11–24.Short sections of different lengths; historical queries, not current congestion rates.0 %10 %20 %30 %Konrad-Adenauer→ Ludwigshafen26 %Kurt-Schumacher→ Ludwigshafen11 %Kurt-Schumacher→ Mannheim9 %Konrad-Adenauer→ Mannheim1 %
Source: MRN / IHK / INOVAPLAN 2020 · Tab. 14 MRN / IHK / INOVAPLAN 2020, Table 14; Google Maps estimates, January 11–24.
Exact values, units and download
bridgedirectionmin_secondsmean_secondsmax_secondsshare_above_1_3_mean_pctlength_kmsourceperiod
Konrad-AdenauerLudwigshafen2370282260.31300000S062020-01-11/2020-01-24
Kurt-SchumacherLudwigshafen4152160110.72400000S062020-01-11/2020-01-24
Kurt-SchumacherMannheim384913390.75700000S062020-01-11/2020-01-24
Konrad-AdenauerMannheim222736110.38700000S062020-01-11/2020-01-24

Download values as CSV

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.

Exhibit 08 · Scenario

How additional minutes accumulate

All inputs are assumptions. Not a measured closure cost or a GDP loss.

SCHYM / RHEIN–NECKAR08 / 08How additional minutes accumulateHypothetical time value · € million · 250 days and €20 per person-hourScenario formula: person-trips × extra minutes / 60 × days × euros per person-hour.All inputs are assumptions. Not a measured closure cost or a GDP loss.Additional minutes per person-trip5 min10 min15 min20 minPerson-trips/day5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Highlighted example: €8.3m; every input is assumed.SCHYM / RHEIN–NECKAR08 / 08How additional minutes accumulateHypothetical time value · € million · 250 days and €20 per person-hourScenario formula: person-trips × extra minutes / 60 × days × euros per person-hour.All inputs are assumptions. Not a measured closure cost or a GDP loss.Additional minutes per person-trip5 min10 min15 min20 minPerson-trips/day5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Highlighted example: €8.3m; every input is assumed.
Hypothetical time value · € million250 days · €20 per person-hourTrips/day5 min10 min15 min20 min5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Example: €8.3 millionEvery input is an assumption.Hypothetical time value · € million250 days · €20 per person-hourTrips/day5 min10 min15 min20 min5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Example: €8.3 millionEvery input is an assumption.
Show compact values
Hypothetical time value · € million · 250 days and €20 per person-hour
Person-trips/day5 min10 min15 min20 min
5,0002.14.26.28.3
10,0004.28.312.516.7
15,0006.212.518.825.0
20,0008.316.725.033.3
25,00010.420.831.241.7
Enlarge chart

Scroll the full chart horizontally and vertically.

SCHYM / RHEIN–NECKAR08 / 08How additional minutes accumulateHypothetical time value · € million · 250 days and €20 per person-hourScenario formula: person-trips × extra minutes / 60 × days × euros per person-hour.All inputs are assumptions. Not a measured closure cost or a GDP loss.Additional minutes per person-trip5 min10 min15 min20 minPerson-trips/day5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Highlighted example: €8.3m; every input is assumed.SCHYM / RHEIN–NECKAR08 / 08How additional minutes accumulateHypothetical time value · € million · 250 days and €20 per person-hourScenario formula: person-trips × extra minutes / 60 × days × euros per person-hour.All inputs are assumptions. Not a measured closure cost or a GDP loss.Additional minutes per person-trip5 min10 min15 min20 minPerson-trips/day5,0002.14.26.28.310,0004.28.312.516.715,0006.212.518.825.020,0008.316.725.033.325,00010.420.831.241.7Highlighted example: €8.3m; every input is assumed.
Assumption; outbound and return journeys count separately.
Assumption; not an observed delay.
Assumed duration of the burden.
Illustrative valuation.
1.667additional person-hours / day
8,33 Mio. €time value across the assumed period

All inputs are assumptions. Not a measured closure cost or a GDP loss.

Source: Own scenario calculation. Scenario formula: person-trips × extra minutes / 60 × days × euros per person-hour.
Exact values, units and download
affected_person_trips_dayadditional_minutesassumed_daysassumed_eur_person_hourhours_dayannual_time_value_eurstatus
5000525020416.666666672083333.33333333hypothetical scenario; not a measured closure cost
50001025020833.333333334166666.66666667hypothetical scenario; not a measured closure cost
500015250201250.000000006250000.00000000hypothetical scenario; not a measured closure cost
500020250201666.666666678333333.33333333hypothetical scenario; not a measured closure cost
10000525020833.333333334166666.66666667hypothetical scenario; not a measured closure cost
1000010250201666.666666678333333.33333333hypothetical scenario; not a measured closure cost
1000015250202500.0000000012500000.00000000hypothetical scenario; not a measured closure cost
1000020250203333.3333333316666666.66666667hypothetical scenario; not a measured closure cost
150005250201250.000000006250000.00000000hypothetical scenario; not a measured closure cost
1500010250202500.0000000012500000.00000000hypothetical scenario; not a measured closure cost
1500015250203750.0000000018750000.00000000hypothetical scenario; not a measured closure cost
1500020250205000.0000000025000000.00000000hypothetical scenario; not a measured closure cost
200005250201666.666666678333333.33333333hypothetical scenario; not a measured closure cost
2000010250203333.3333333316666666.66666667hypothetical scenario; not a measured closure cost
2000015250205000.0000000025000000.00000000hypothetical scenario; not a measured closure cost
2000020250206666.6666666733333333.33333334hypothetical scenario; not a measured closure cost
250005250202083.3333333310416666.66666667hypothetical scenario; not a measured closure cost
2500010250204166.6666666720833333.33333334hypothetical scenario; not a measured closure cost
2500015250206250.0000000031250000.00000000hypothetical scenario; not a measured closure cost
2500020250208333.3333333341666666.66666667hypothetical scenario; not a measured closure cost

Download values as CSV

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.

Michael Schymura · As of September 4, 2026. Sources and methodological boundaries belong with every reuse.