Ludan-Tech: The Rail Backlog Looks Strong, but What Actually Converts and When?

What This Follow-up Is Isolating

The main article already established that 2025 was not weak because Ludan-Tech lacked work. It was weak because transport backlog, revenue recognition, and balance-sheet timing did not line up. This follow-up isolates the question that really determines whether the technology thesis is improving: what inside the rail backlog is already close to revenue, what is still sitting in design, and what has not yet become a recurring maintenance layer at all.

That matters because the headline has almost everything a reader wants to see: new light-rail contracts, a strong ticketing position, and the promise of long-duration service revenue. But economically, these contracts live on three different clocks. One layer is already being measured through percentage of completion. One layer is still in design and system definition. And the maintenance layer, which is usually the cleaner one economically, is in some cases still ahead of operation and in some cases has not yet been ordered under a separate service agreement.

Three points matter right away:

• Recognition is slower than the headline. In the Gush Dan light-rail project, which started in 2024 and is expected to run until around 2030, percentage of completion was only 17% at the end of 2025. Cumulative recognized revenue was NIS 10.9 million, while NIS 53.5 million was still unrecognized.
• The broader technology backlog is still back-end loaded. Out of NIS 327.8 million of technology-segment backlog, only NIS 102.3 million sits in 2026, while NIS 225.5 million sits after 2026.
• Maintenance supports the thesis, but mostly later. The company explicitly says that more meaningful recurring maintenance revenue is expected only from 2027, with the start of the Jerusalem green line and the extension of the red line.

The Wider Timing Profile Explains Why New Wins Do Not Become Profit Immediately

The technology-segment backlog table is not a pure rail table, but it does explain why the new wins do not automatically make 2026 a breakout year. At year-end 2025, the segment backlog stood at NIS 327.8 million. Of that, NIS 24.9 million was scheduled for Q1 2026, NIS 24.0 million for Q2, NIS 26.0 million for Q3, and NIS 27.4 million for Q4. Everything else, NIS 225.5 million, was pushed into 2027 and beyond.

This is the first point that cools an overly optimistic read. If one only looks at the headline number, NIS 327.8 million, it is easy to assume the problem is already behind the company. But once the schedule is unpacked, it becomes clear that a large part of the backlog does not even sit inside the next reporting window.

There is also a more interesting nuance here. The company explains that the portion scheduled beyond the end of 2026 is mainly attributable to long-term maintenance. That is only partly true. The table itself shows that the post-2026 bucket still contains NIS 114.5 million of maintenance against NIS 111.0 million of build contracts. In other words, the long tail is not a clean annuity bucket. Nearly half of it is still project work.

As of the report date, the company also says there were no material changes in backlog relative to year-end 2025. So between year-end and publication, there was no new jump that materially pulled backlog closer to revenue. The headline remained strong. The timing profile remained largely the same.

The Material Rail Projects Already Show That Conversion Is Slow

This is where the read moves from the wider table to the rail disclosures themselves. In the very material Gush Dan project, the company describes a contract to design, specify, supply, and install a smart ticketing system for a light-rail line. The start date is 2024, the expected completion date is with full line operation in 2030, and percentage of completion at the end of 2025 was only 17%.

The numbers are direct. Estimated total revenue slipped slightly to NIS 64.5 million, cumulative recognized revenue rose to NIS 10.9 million, and unrecognized revenue still stood at NIS 53.5 million. At the same time, the company characterizes expected gross profitability as similar to the average for the segment. That matters, because the filing is not describing an unusually high-margin rail project. It is describing a large and long-duration one.

The wider public-transport project group tells a similar story. At year-end 2025, there were 18 public-transport projects in execution and none had been completed. Out of total estimated revenue of NIS 230.1 million, NIS 128.2 million still had not been recognized. So even beyond one specific project, the message is the same: the contracts exist, but a meaningful part of the economics still sits ahead.

The newer Jerusalem contracts reinforce that reading. In the August 2025 contract, with scope of about NIS 30 million and euro linkage, the company says explicitly that the work was still in design and system-definition at the report date, and that execution is expected to last about five years. In December 2025, another ticketing contract was added with estimated scope of about NIS 25 million, again over roughly five years, and the company says the expected profitability is similar to comparable projects. That strengthens the strategic position, but it does not prove near-term margin acceleration.

The outlook for the coming year also sounds more cautious than the headline. The company says equipment orders for the light-rail projects are expected to be issued during the coming year, but that the bulk of the equipment, its delivery to the platforms, and its installation are expected only in the fourth quarter of 2026. That wording matters because it almost summarizes the whole debate: the contracts are there, but the main equipment layer is not there yet.

Billing Helps, but It Does Not Make the Backlog Hard

This is one of the most important distinctions in the whole continuation. Rail projects are not structured so that all the money waits until final delivery. Consideration is generally paid according to progress and defined milestones. In some cases, parts of the payment are also subject to approval by the ministry or the final customer. And where equipment makes up a large part of the project, 50% or more, the contract structure often includes a milestone of up to 20% of consideration once purchase orders are issued to equipment manufacturers.

That helps bridge financing. It does not make the backlog hard revenue. The filing itself explains that this milestone is used to fund supplier advances for project equipment. So part of the early billing is there to finance the supply chain, not to prove that the project has already crossed into easy revenue and profit conversion.

At the same time, the customer protection layer remains strong. In general, the company says customers can order a work stop, and in most cases the company is entitled only to payment for work already performed, without compensation for lost future profit. In the Gush Dan project there is also an explicit suspension mechanism, where the company is entitled to reimbursement of direct unavoidable costs only if suspension exceeds three months, and after twelve consecutive months of suspension either side may cancel. In the August 2025 Jerusalem contract there is also a cancellation right if the main contract is cancelled or for convenience.

The guarantees add another layer. In the rail contracts disclosed in the filing, execution guarantees are not trivial: 10% of consideration in the older Jerusalem project, 10% in Gush Dan, and 15% in the August 2025 Jerusalem contract, stepping down to 5% during warranty after completion. So backlog quality is not just about whether a contract has been signed. It is also about how much working capital, guarantee capacity, and banking headroom it consumes on the way to conversion.

Maintenance Is the Better Layer, but It Mostly Arrives Later

There is good news here, just not immediate news. The company says that in public transport the maintenance period usually runs throughout the concession term, and that customers in this field usually exercise the maintenance option through the end of the concession. Economically, this is the cleaner layer: payments are fixed, quarterly or semiannual, and are usually paid at the beginning of the period for which the service is provided.

But timing matters here as well. The company explicitly says recurring maintenance revenue is expected to become more meaningful only from 2027, with the start of the Jerusalem green line and the extension of the red line. So 2026 does not yet benefit from the full service layer that a rail-backlog headline may imply.

The best example is the older Jerusalem contract from 2021. Beyond about NIS 40 million of system supply, it also includes 20 years of maintenance after project completion, at roughly NIS 2.5 million per year. That is exactly the kind of economics the market wants to see: installed base turning into long-duration service. But it sits after project completion, not before it.

By contrast, the August 2025 Jerusalem contract already includes pricing for operation and maintenance in its bill of quantities, but those services, if ordered, will be ordered by the operations-and-maintenance contractor under a separate agreement. So not every new light-rail win instantly creates signed recurring revenue.

That is the key distinction. The rail backlog does build a future maintenance base. It simply does not build all of it at once, and certainly not all of it inside 2026.

Bottom Line

Ludan-Tech’s rail backlog is real, material, and supportive of Shimekotech’s strategic standing in ticketing. But it is not equivalent to immediate revenue, and certainly not to a fully active maintenance layer. As of year-end 2025, the economics of that backlog are split between projects still sitting in design, projects progressing slowly through percentage of completion and milestone gates, and a better-quality maintenance layer that becomes more meaningful mainly from 2027 onward.

So the right read is not whether the backlog is strong or weak. The right read is that the backlog is strategically strong, but its conversion quality is still only partial. There is visibility. There is installed base. There is a good competitive position in light-rail ticketing. What is still missing is proof that the new wins are moving from design into equipment orders, that the existing projects are stepping materially higher in completion, and that maintenance is actually beginning to carry a larger part of segment revenue.

What will decide the next read:

• Execution: whether 2026 actually brings equipment orders, delivery, and installation rather than only more design progress.
• Recognition: whether the Gush Dan project moves materially beyond 17% completion and begins to release a more meaningful recognition pace.
• Maintenance: whether the Jerusalem service layer starts contributing in a way that justifies the case for stronger recurring revenue from 2027 and after.