Will Israel Railways' Capacity Projects Actually Unlock the Bottleneck?
Israel Railways' annual report shows that easing the network bottleneck depends not on one flagship project, but on an execution stack: electrification, ERTMS, Route 431, the Eastern Railway and the fourth Ayalon track. The problem is that some links have already slipped and some still do not have a disclosed completion date.
The main 2025 article argued that Israel Railways no longer has a demand problem. It has an execution problem. This follow-up isolates the most important piece of that thesis: whether the company's capacity project stack is actually close to clearing the bottleneck, or whether it still looks more like a heavy execution backlog with too many moving parts.
The answer that emerges from the report is fairly sharp. This is not one project. It is a chain. Electrification, ERTMS, Route 431, the Eastern Railway and the fourth Ayalon track are supposed to intersect to create real capacity, operating flexibility and higher frequency. But the timelines disclosed in the report do not close together. Core electrification was updated to March 2027, Route 431 to the fourth quarter of 2027, the Eastern Railway to the third quarter of 2027 including line electrification, ERTMS to 2028, and the section of the fourth Ayalon track that is under the company's responsibility only to the fourth quarter of 2029, while the estimated completion date for the full project is December 2031. At the same time, the follow-on electrification of Route 431, the Eastern Railway and the Ashkelon-Goral section still appears without a stated engineering-readiness date.
What matters even more is that this story no longer sits only in the strategy section. In the impairment-indicator review, the passenger segment's revenue assumptions for 2025 through 2028 already incorporate electrified train operations, added capacity, the opening of the Eastern Railway and a line along Route 431. In other words, the capacity stack is already inside the economic model management is using for the future. A delay is therefore not just a delay in passenger convenience. It is a delay in part of the company's own forward operating logic.
The bottleneck is a chain, not a project
The table below is the right way to read the story. The question is not how impressive each project looks on its own, but where each one depends on the others.
| Link | What it is meant to unlock | Disclosed target | What is still open |
|---|---|---|---|
| Electrification | Electric traction, shorter travel times, higher frequency, more cars and better punctuality | March 2027 under addendum no. 9 | Follow-on electrification for Route 431, the Eastern Railway and Ashkelon-Goral still has no engineering-readiness date; parts of addendum no. 11 were removed from SEMI after repeated breaches |
| ERTMS | Safety upgrade and capacity increase, especially at bottlenecks | Full project expected in 2028 | The project has three layers and three suppliers; delays were already tied to missing foreign experts and postponed testing |
| Route 431 | Direct rail connection between southern Gush Dan and Jerusalem/Modiin, plus more operating flexibility | Fourth quarter of 2027 | Labor shortages, sandy-soil tunneling at Mavo Ayalon and delays in Solel Boneh's work |
| Eastern Railway | Eastern freight corridor, strategic alternative to the coast and Ayalon, and future passenger service | Third quarter of 2027, including line electrification | The project is split between Israel Railways and Netivei Israel, and the report also cites utility-relocation delays and war effects |
| Fourth Ayalon track | Raising Ayalon capacity from 17 to 26 trains per hour per direction and releasing the system-wide bottleneck | Fourth quarter of 2029 for the section under Israel Railways; December 2031 as the estimated completion date for the full project | Dependence on Netivei Israel milestones, exposure to rainy-season constraints, and a newly transferred HaHagana-Ganot section whose schedule and budget are still being assessed |
The practical meaning of that table is that the railway is unlikely to get a single clean "unlock" date. Even if Route 431 and the Eastern Railway move well in 2027, their follow-on electrification is still open. Even if ERTMS is a proven capacity lever, it sits on a 2028 timetable. And even if the fourth Ayalon track is the heart of the Ayalon solution, its disclosed timeline runs later. That is why the gap between physical track opening and usable capacity release may be wider than any single headline on any one project suggests.
ERTMS matters here as well. The company explicitly says that once the system is in operation, 3 additional peak-hour trains per direction will be able to run in the Ayalon corridor on the existing infrastructure. That matters because it shows that Ayalon capacity does not depend only on the fourth track. It also depends on the signalling and control layer. Anyone reading the fourth track as the only answer to the bottleneck is missing half the story.
That chart adds another important layer. Even in projects that are already in execution, the remaining spend is still material. In the fourth Ayalon track, for example, the section under the company's responsibility still carries an estimated ILS 1.456 billion to completion against a company-attributed budget of about ILS 1.862 billion, while the full project is described at roughly ILS 5 billion. The Eastern Railway and electrification also still sit on meaningful remaining execution, not near-finished delivery.
Where the chain has already stretched
The report does not try to hide the operational reality. During the war period, development activity was halted completely for a certain time in order to protect employees, consultants and contractors. Suppliers from foreign countries returned to their home countries, and even after the fighting subsided it took additional time for foreign contractors and workers to return to full activity. At the same time, the company received supplier requests for expected schedule delays, sought state approval for extension frameworks, and then states explicitly that such frameworks were not approved.
That is not a footnote. The company says clearly that several of its main projects, Route 431, electrification, ERTMS and the Eastern Railway, were affected by the war and by Operation Rising Lion in terms of project completion schedules. It also explains how: shortages of skilled labor, shortages of engineering equipment, and the non-arrival of foreign experts. As of the report date, after Operation Roaring Lion, the company was operating 55 stations out of 67. That shows how far the network still is from a stable execution environment.
The report also provides project-specific friction points:
- In ERTMS, the company emphasizes that the project is built from three different layers, each with a different supplier. This is an interface chain, not a single contract. When foreign experts do not arrive and tests are postponed, the issue is not just a technical delay. It is a system-layer delay.
- In Route 431, the company points to work next to busy roads and interchanges, multiple contractors, the need for schedule synchronization, sandy-soil tunneling at Mavo Ayalon and delays in Solel Boneh's execution. That is no longer an abstract infrastructure risk. It is a very specific execution bottleneck list.
- In the Eastern Railway, the company also points to delays in relocating third-party utility infrastructure. That means that even when budget exists and the contractor is in place, some links are not fully under the railway's control.
- In the fourth Ayalon track, the dependence on Netivei Israel is fully exposed. The report says delays in its milestones may affect Israel Railways' milestones, and it adds a seasonal constraint because in early stages construction next to the stream is possible mainly in spring and summer.
This is the core point. A railway capacity project does not stall only because of funding, and not only because of one contractor. It stalls at interfaces, permits, seasons, experts, electrification, signalling and sections executed by other bodies. Israel Railways is almost saying that outright in its own annual report.
What the market could miss, the assumptions are already running ahead
A reader who stays only in the risk section might think this is still mainly a long-term strategic issue. Note 13 shows it is already closer than that. In the 2025 impairment-indicator review, the passenger segment's revenue forecasts for 2025 through 2028 incorporate the current development and operating agreement together with updated multi-year operating parameters, and explicitly include the move to electrified train operations, added capacity, the opening of the Eastern Railway and a line along Route 431.
On the cost side, the same review already includes known exceptional future costs, including ETCS maintenance, changes in the rolling-stock mix and a multi-year hiring plan. That matters because management is not assuming only upside. It is also assuming the operating burden that comes with part of the new system. The right reading of the report is therefore not "if these projects succeed one day". The right reading is "some of these projects are already embedded in the scenario the company is using to test itself".
Management does add an important qualifier. It says the 2025 review implies only a decline of tens of millions of shekels in value in use, an amount that remains well below the excess of recoverable amount over carrying value, so no full new valuation was required. That means the accounting cushion still exists. But it does not cancel the analytical point. Future capacity is no longer a distant aspiration. It is part of the model.
That leads to the more important implication. As long as slippage stays isolated, the company may still be able to absorb it inside that cushion. But if delays extend across several links at once, or if the interfaces between electrification, signalling and the Ayalon corridor keep slipping together, the gap between the operating assumption and actual delivery will become more meaningful.
So will the bottleneck actually clear
There are positives in the report, and they deserve full weight. The targets themselves are more explicit than in many other infrastructure stories. ERTMS already received PTO approval in 2024 for the Navon-Herzliya section. The fourth Ayalon track presents, for the first time, a concrete output metric, from 17 to 26 trains per hour per direction. Route 431 and the Eastern Railway already sit on 2027 target dates rather than vague "later on" language. Addendum no. 9 to electrification has been signed and includes reinforced work teams, new milestones and an updated execution framework.
But the overall picture is still one of a long bridge period, not of a solved bottleneck. Core electrification has moved to March 2027. The follow-on electrification for Route 431 and the Eastern Railway still has no date. ERTMS sits in 2028. In Ayalon, the company itself writes that its part is due in the fourth quarter of 2029, while the full project is estimated for December 2031. The reasonable implication is that 2026 through 2028 are years in which parts of the puzzle may advance, but not necessarily close together.
That is exactly the point a reader may miss if they settle for a project list. Track opening, electrification, signalling and corridor capacity are not the same milestone. The company itself ties future capacity to electrification, ERTMS, the Eastern Railway, Route 431 and the fourth track. The more careful conclusion is therefore that the bottleneck clears only when the chain closes, not when one link gets inaugurated.
Conclusion
If this continuation has to be reduced to one line, it is this: Israel Railways has already shown in 2025 that the demand is there, but it has not yet shown that the engineering and delivery stack around its main capacity projects is truly close to releasing the bottleneck.
The current thesis: Israel Railways' capacity stack is a dependency story, not a single-project story. As long as electrification, ERTMS, Route 431, the Eastern Railway and the fourth Ayalon track do not converge in practice, the network bottleneck is not really opening. It is mainly receiving a new target date.
Disclosure: Deep TASE analyses are general informational, research, and commentary content only. They do not constitute investment advice, investment marketing, a recommendation, or an offer to buy, sell, or hold any security, and are not tailored to any reader's personal circumstances.
The author, site owner, or related parties may hold, buy, sell, or otherwise trade securities or financial instruments related to the companies discussed, before or after publication, without prior notice and without any obligation to update the analysis. Publication of an analysis should not be read as a statement that any position does or does not exist.
The analysis may contain errors, omissions, or information that changes after publication. Readers should review official filings and primary sources before making decisions.