Israel Railways follow-up: SEMI cancellation and the cost of the capacity chain

The SEMI cancellation strengthens Israel Railways' control over one of the most sensitive links in the capacity chain, but it does not shorten the path to usable capacity on its own. The important point is not only the legal win. It is the move from a dispute with one contractor to a broader replacement test: who performs the work, at what pace, and with what budget impact. The earlier article on the capacity project chain framed electrification, Route 431, the eastern rail line, and ERTMS as interdependent links. The first quarter adds a new fact: the company did not only remove parts of SEMI's work scope, it also notified SEMI after the balance-sheet date that the full agreement would be canceled and that guarantees would be forfeited. That is progress in enforcement, not proof of execution. The next proof point is not another court decision, but an updated schedule showing that replacement contractors and approved budgets can put electrification back on track without delaying the rest of the capacity chain.

The cancellation removes a legal block, not the execution test

SEMI sued the company on April 5, 2026 and sought enforcement of the agreement to design, build, and maintain railway electrification infrastructure. The claim followed the company's partial cancellation notice: removal from SEMI's scope of sections C and D of the eastern rail line and Route 431, where the contractor had not yet started work, with replacement contractors appointed for those sections.

The legal stage has so far gone in the company's favor. The District Court rejected the request for an interim injunction on the same day, and on May 15, 2026 it also rejected the request for a permanent injunction. On May 20, 2026 the company notified SEMI that the full agreement would be canceled within 14 days because of fundamental breaches, and also notified SEMI that it would forfeit the guarantees held to secure the contractor's obligations.

The positive reading is clear: the company is not stuck with a contractor it says breached the agreement, and it gained legal room to move to replacements. But that is only the first link. The filings do not provide a new replacement execution timetable, the amount of guarantees to be forfeited, or a separate estimate for replacement cost. So there is no basis yet to claim that the cancellation has accelerated electrification. The narrower and more important conclusion is that the risk has moved from whether the company can break away from SEMI to whether it can replace SEMI without adding another delay to the chain.

The capacity chain is still a multi-billion-shekel project stack

The cost is not only in the SEMI contract itself. It sits inside a project chain where each link can delay the others: track, electrification, signaling, rolling stock, and station capacity. So the right way to cut the event is not "a contractor was canceled", but how much usable capacity still has to pass through actual execution.

These numbers are not the cost of canceling SEMI. They show what still has to happen around that cancellation for the network to receive usable capacity. During the quarter itself, the company already invested about NIS 181 million in line projects, including the eastern rail line, Route 431, the fourth Ayalon track, and the coastal line doubling, another about NIS 132 million in infrastructure such as ERTMS and grade separations, and about NIS 56 million in the electrification project. In other words, while the SEMI dispute escalated, the company kept putting capital into the same links.

This is where the economic cost of the capacity chain begins. Even if development is state-funded, the funding source is not the only issue. A delay in electrification can reduce the benefit of a new rail line, a delay in signaling can limit the benefit of the fourth Ayalon track, and a delay in replacement contracting can leave civil infrastructure ready without full operating capability. For bondholders, this is less an immediate liquidity event and more a credibility test: whether the development program is advancing at a pace that supports the service, demand, and compensation assumptions for the next few years.

SEMI is not the only completion risk in the project stack

The note on lawsuits and payment demands sharpens the same point from another angle. Near completion of development projects, contractors sometimes submit demands for additional payments beyond the original agreements. As of the reporting date, the company had received demands from various contractors, mainly around construction of fixed assets, in amounts about NIS 902 million above the provision included in the financial statements.

The company estimates that the probability it will be required to pay material amounts beyond those already included in the development budget is below 50%, and that any such amounts should be part of the projects' development budget. Still, if it is required to pay the full demands, it does not have state budget approvals for that full amount. That does not mean the debt is under immediate pressure, but it does show that the SEMI dispute is not an isolated exception inside a smooth execution system. Around the development projects there is a wider final-account layer, and that can turn execution delay into a budget dispute.

The impact of Operation Shagat HaAri on the projects is also still under review. The company cannot estimate the future impact of security uncertainty on its operations and projects, and lists possible effects including development-project delays, state decisions, regulation, and government support. That is another uncertainty layer, but it does not change the conclusion. After canceling SEMI, the company needs to show that the problem was not just one contractor, but a chain it can manage despite contractors, budgets, and security conditions.

The next test is replacement without another delay

The rest of the SEMI story will be decided less in court and more in the schedules for Route 431, the eastern rail line, electrification, and ERTMS. Canceling the agreement and forfeiting guarantees improve the company's position against a contractor it says did not perform, but they do not prove that capacity will arrive faster. The current conclusion is cautiously positive: it is better for the company to cut off a breaching contractor than to remain stuck with it, but after the cut the burden of proof is higher. An update showing replacement contractors, clear milestones, and sufficient budget approvals would support the view that the cancellation removed a bottleneck. Without that schedule, the cancellation will look like another sign that the company's capacity chain remains costly, dependent, and exposed to delays.