Israel Shipyards: When Does the Reshef Backlog Really Reach Earnings
This follow-up isolates the question the main article left open: the Reshef backlog is already large and visible, but by the end of 2025 only about 15.6% of the shipyard's remaining performance obligations were expected to be recognized within a year. Until delivery timing, concentration and working capital line up, backlog is still not the same thing as earnings.
Reshef Is Already In The Revenue Line, But Most Of The Recognition Still Sits Ahead
The main article already established that 2025 was an expensive transition year: Reshef, the silos and the Chevron logistics work had already entered the picture, but profit had not yet caught up. This follow-up isolates only the Reshef thread, because that is where the core timing gap now sits between backlog and earnings.
The headline number is known. At year-end 2025 the shipyard had NIS 2.645 billion of performance obligations not yet satisfied or only partly satisfied. What matters more is the recognition curve: only NIS 412.4 million, about 15.6% of the amount, was expected to be recognized within a year. Another NIS 687.0 million sat in the one-to-two-year bucket, and NIS 1.545 billion was pushed beyond that.
That is the real explanation for the gap between the headline and the statements. The five-ship Reshef agreement was signed in December 2024, but the board report says explicitly that the contribution in 2025 was still low because of the early stage of the project and the revenue-recognition policy. Only from the third quarter of 2025 did the pace of progress start to lift activity, and management itself marks 2027 and 2028 as the peak years of the project.
Put differently, Reshef has already reached the shipyard, but it has not yet fully reached earnings. Anyone looking at a NIS 2.4 to 2.6 billion backlog and jumping straight to 2026 is missing the shape of the curve: most of the project still sits beyond the first 12 months, so the real earnings contribution is built in stages, not all at once.
The Second Half Already Showed A Ramp, But Not A Regime Change
The good news is that conversion has already started. In the March 2026 presentation the shipyard segment showed revenue of NIS 101.4 million in the first half of 2025 and then NIS 169.8 million in the second half. Segment EBITDA moved in the same direction, from NIS 6.1 million to NIS 25.0 million.
So it would be wrong to say that Reshef still has no footprint in the numbers. It already does, and quite sharply, especially from the third quarter onward. The board report says fourth-quarter shipyard revenue rose to NIS 83.0 million from NIS 64.6 million in the comparable quarter, while segment EBITDA rose to NIS 15.0 million from NIS 9.4 million.
But that is also where the caution starts. In the same 2025 presentation the shipyard accounted for only 18% of group EBITDA mix. That is an important number because it says Reshef is already moving the needle, but it still does not define the earnings structure of the group. In 2025 terms, the shipyard moved from a stage where Reshef was mostly a backlog story into a stage where it clearly supports revenue recognition. It has not yet moved into a stage where Reshef is the dominant earnings engine.
There is another line in the report that cools expectations. The company says explicitly that the expected profitability of the agreement, as of the report date, is not materially different from the profitability it usually earns in similar Ministry of Defense sole-supplier work. That is critical. A very large contract does not automatically mean an unusually high-margin contract. The question is therefore not only when the revenue arrives, but at what pace and what it leaves behind at the earnings line.
Customer Concentration Is Real Even If The Company Does Not Frame It As Permanent Dependence
The customer disclosure in the shipyard segment shows how concentrated the year has already become. Customer A jumped to NIS 185.6 million in 2025, from NIS 64.4 million in 2024. At the whole-company level that is already 12% of revenue, versus 5% a year earlier.
The company immediately adds an important qualifier: because of the project-based nature of the activity, a year in which one project moves at a fast pace creates financial dependence on that customer in that specific year, but beyond that the shipyard does not depend on any specific customer or customers. That framing is fair, but it needs to be read fully. It does not erase concentration. It only explains that the concentration comes from the timing of recognition rather than from a permanently narrow commercial base.
That is exactly the relevant point here. Even if the shipyard's customer base is broader over a full multi-year cycle, 2025 to 2028 can still be years in which one large defense program moves a big part of the segment's numbers. A milestone delay would therefore not be only an operational issue. It would also move revenue, EBITDA and market interpretation from quarter to quarter.
There is another link back to economics. The company says that sole-supplier work with the Ministry of Defense can limit profitability and gross-margin rates. In other words, the large customer brings visibility and scale, but not unlimited pricing power. Anyone turning the size of the backlog directly into an assumption of unusually strong profitability is reading too much into the contract value alone.
Working Capital Is Already Deep Inside The Program
This is where the story becomes more interesting than the backlog itself, because Reshef does not reach the statements only through a timeline. It also reaches them through the balance sheet.
In the statement of financial position the company explains that the rise in cash and short-term investments, roughly NIS 49 million, came mainly from advances received in shipyard projects. But in the very same statement, advances to suppliers rose to NIS 49.3 million from NIS 9.1 million, mainly because of supplier payments in the Reshef project, and inventory rose to NIS 132.9 million from NIS 113.1 million, mainly because of procurement for the project.
The construction-contract note adds the other half of the picture. At year-end 2025 the company had NIS 43.6 million of contract assets, but it had already recorded NIS 115.3 million of contract liabilities, and management says the increase came from advances received in shipyard projects.
| Balance-sheet layer | 31 Dec 2024 | 31 Dec 2025 | What it means in practice |
|---|---|---|---|
| Contract assets | NIS 46.5m | NIS 43.6m | Recognition ahead of billing did not expand at year-end |
| Contract liabilities | 0 | NIS 115.3m | The customer is already advancing cash against milestones |
| Advances to suppliers | NIS 9.1m | NIS 49.3m | Part of that cash has already moved down the production chain |
| Inventory | NIS 113.1m | NIS 132.9m | Reshef-related procurement is already sitting on the balance sheet before delivery |
The implication runs in two directions. On one side, Reshef does not need to wait for full delivery to affect liquidity. The customer is already providing cash, and that helps finance the build. On the other side, this is not free cash. During 2025 alone, advances to suppliers and inventory increased by a combined NIS 60.1 million, and the company itself ties both lines mainly to the Reshef program.
That is easy to miss if one looks only at backlog. A long-cycle defense backlog does not become net earnings automatically. First it moves through suppliers, raw materials, milestones and contract accounting. So even when the project partly finances itself through advances, it can still load working capital and keep the earnings line behind the headline backlog.
What Would Prove That Reshef Really Reached Earnings
From here the test can be reduced to four straightforward checkpoints:
| Checkpoint | What would count as real progress | What would be a yellow flag |
|---|---|---|
| Recognition pace | A meaningful portion of the NIS 412.4m due within a year actually appears in 2026 revenue | Another year in which the main story remains in backlog rather than in reported activity |
| Contribution quality | The shipyard moves above its current 18% share of group EBITDA without relying on one unusually strong quarter | Revenue rises, but profitability still looks too similar to the early-stage 2025 profile |
| Working capital | Customer advances keep supporting execution without another jump in inventory and supplier advances | The program keeps absorbing cash faster than it releases it |
| Concentration | Milestones keep the large customer as a source of visibility rather than volatility | A delay from one customer again shifts the entire segment reading |
That is really the answer to the title question. The Reshef backlog starts to reach earnings when it stops being mainly backlog and becomes revenue, margin and manageable working capital at the same time. By the end of 2025 only the first part of that process had clearly begun.
Conclusion
Reshef is no longer only a slide-deck story. It already lifted the pace of activity in the second half of 2025, it already created much higher customer concentration, and it already left a visible footprint on the balance sheet through advances, inventory and supplier prepayments.
But anyone looking for the point where backlog becomes earnings needs to stay disciplined. At year-end 2025 only about 15.6% of performance obligations were expected to be recognized within a year, the company itself points to 2027 and 2028 as the peak years, and the expected profitability of the contract is not presented as unusual relative to the shipyard's regular defense work.
So the short answer is that Reshef has already reached revenue, should become materially more visible in 2026, but only becomes a full earnings engine if 2027 to 2028 confirm three things together: continuous recognition, profitability that does not erode, and working capital that does not swallow the customer advances on the way.
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.