Arasal: Is the HUMS Backlog a Real Future Engine or a Long-Dated Option?
Arasal's HUMS backlog looks large against 2025 revenue, but 74.1% of it sits in 2027 and beyond, while the segment itself fell from NIS 22.2 million of revenue in 2024 to NIS 2.1 million in 2025 and moved from profit to loss. This follow-up tests whether the HAL relationship, the smart-sensor roadmap and the pilot work already support a real commercialization engine, or still describe a long-dated option.
The main article already framed Arasal's core gap: consolidated backlog jumped, but profit still did not turn that into a clean story. This follow-up isolates HUMS because that is where most of the upside option sits. It is also the place where 2025 delivered the sharpest contradiction between narrative and economics.
The numbers are blunt. HUMS revenue fell to NIS 2.084 million in 2025 from NIS 22.216 million in 2024. Gross profit flipped from NIS 16.009 million to a gross loss of NIS 3.995 million, and operating profit swung from NIS 9.405 million to an operating loss of NIS 7.199 million. And yet HUMS backlog stood at NIS 21.47 million at year-end and remained unchanged close to publication.
That creates the real question. Is this backlog already the base of a future engine, or is it still a credible but long-dated option with weak near-term conversion.
- First finding: the backlog exists, but the segment's 2025 economics broke down.
- Second finding: 74.1% of HUMS backlog is scheduled for 2027 and beyond, and only 25.9% is scheduled for 2026.
- Third finding: the commercialization path through HAL and the Indian government customer is real, but even after platform adaptation and actual deliveries, 2025 did not show an income stream that justifies calling HUMS an engine.
- Fourth finding: the smart sensor, the grant and the pilots expand the technology option, but they still do not create recurring revenue proof.
2025 Showed That The Problem Is Conversion, Not Technology
If you look only at backlog, the story can sound attractive. If you look at 2025 economics, the picture is almost the opposite. In 2024 HUMS generated 41.1% of company revenue. In 2025 that same segment fell to only 5.0% of the group's sales. That is not a normal slowdown. It is a collapse in business weight.
That chart is the core of the continuation thesis. It shows that this is not just a revenue delay story. The segment also lost profitability and the ability to absorb its own cost base. So a reader who treats HUMS backlog as a substitute for 2025 results is missing the point. The backlog says future work exists. It does not say the segment has already proven stable commercialization economics.
The year-end exit rate is even weaker than the full-year numbers suggest. HUMS revenue in the first half of 2025 was NIS 1.884 million. Since full-year revenue was only NIS 2.084 million, the implied second-half revenue was roughly NIS 0.2 million. That is a very weak exit rate for a segment that is supposed to be backed by a NIS 21.47 million backlog.
There is another important nuance. The company says that, as of publication, it had no material agreements in HUMS. That does not mean there is no backlog, because the backlog is clearly disclosed. It does mean there is no single disclosed HUMS contract that alone anchors the story. In practice, the read still depends on a collection of orders, adaptations, tenders and negotiations, not on one disclosed commercial anchor that shortens uncertainty.
The Backlog Is Real, But Most Of It Sits Too Far Out
The good news is that the backlog does not disappear by publication. It stood at NIS 21.47 million at year-end 2025 and remained at the same level close to publication. The less encouraging news is that its revenue timing is weak for anyone looking for a near-term engine.
The near-dated part of the backlog is only NIS 5.552 million, and all of it is concentrated in the second quarter of 2026. The first, third and fourth quarters of 2026 show no expected HUMS revenue recognition at all. NIS 15.918 million, or 74.1% of the backlog, is pushed into 2027 and beyond.
That matters because, on first read, a NIS 21.47 million backlog looks huge against 2025 HUMS revenue of NIS 2.084 million, about 10.3 times larger. But that ratio is so high because two things happened at the same time: revenue became extremely weak in the base year, and backlog shifted outward. So this is more a backlog of duration than a backlog of near-term visibility.
Even inside 2026, the backlog does not look like a smooth supply stream. It looks like one recognition window in the second quarter, without a quarterly sequence that would suggest a stabilized commercialization path. If that window slips, the whole read can stretch again very easily.
The HAL Commercialization Path Exists, But 2025 Did Not Confirm It As An Engine
The positive side of the thesis is not imaginary. The company has already crossed several important milestones. It developed HUMS systems for the Israeli Air Force Apache fleet, supplied the full fleet, and says the system received full certification and licensing from its customers and from the relevant foreign supervisory bodies. This is not a lab story. It is operational proof.
The India expansion path is not just theoretical either. Over the past three years the company adapted HUMS for HAL's LIGHT COMBAT HELICOPTER and LIGHT UTILITY HELICOPTER after winning two HAL tenders. It also says that during 2024 it supplied 22 systems for the LIGHT UTILITY HELICOPTER. In parallel, during 2025 it supplied HUMS systems to a government customer in India for engines, propulsion systems and helicopters, and it says it is in talks with potential customers for fighter-jet engines, UAVs and additional helicopter types.
The problem is that the 2024 revenue jump did not turn into a stable path in 2025. Quite the opposite. 2025 showed that even after platform adaptation, initial deliveries and real customer relationships, the segment can fall back to almost negligible revenue.
| Layer | What is already proven | What is still missing | Why it matters |
|---|---|---|---|
| Apache, Israeli Air Force | Full deployment, certification and licensing | Broad replication across additional platforms | This is proof of capability, not a growth engine by itself |
| HAL in India | Adaptation to two helicopters, delivery of 22 systems in 2024, additional deliveries in 2025 to an Indian government customer | Annual order flow that creates recurring revenue and profitability | This is the closest path to serial commercialization |
| Talks for more helicopters, fighter engines and UAVs | An active opportunity pipe | Named contracts and visible delivery timing | Without conversion from talks to orders, the narrative stays forward-looking rather than present-tense |
The path is still long for a clear reason. In civil aviation, HUMS approval is described as a long-term process that requires material resources, and the company explicitly says it needs partnership with the original manufacturer or with major customers such as armies or government companies. Its business strategy is also built around cooperation with original manufacturers in order to ease market entry. In other words, the bottleneck is not only technological. It is also regulatory and commercial, and it requires strong route-to-market anchors.
That is also the right way to read HAL. The relationship matters because it represents exactly the path the company wants: a large original manufacturer, platform adaptation, and the expectation of future orders for hundreds of systems. But as of the end of 2025, that expectation still had not translated into a revenue and profit engine that could hold for a second year in a row.
The Smart Sensor Expands The Option, It Does Not Prove Commercialization
The smart sensor is probably the most interesting strategic asset inside the HUMS story, because it is supposed to solve the heavy and expensive installation problem. The company says these smart sensors with edge-processing capability should allow fast and lower-cost integration of monitoring capability even when only partial information exists about the monitored system. That is why it connects the project to markets it previously failed to enter because of installation challenges and cost.
But here too the distinction between potential and commercialization matters. In June 2023 the Israel Innovation Authority approved a research grant of up to NIS 1.89 million for the development of new HUMS systems based on edge processing. By publication, about NIS 1.69 million to NIS 1.70 million had already been received, and the remaining amount was received in 2026. That reduces the development burden on the company. It does not create recurring revenue.
The list of pilots is also stronger technologically than commercially. The company describes demonstrations and pilots involving Israel Railways, civilian and military vessels, freight rail cars, Industry 4.0, armored vehicles and heavy vehicles. It also advanced a pilot with Israel Railways, and that agreement includes participation in pilot implementation costs and a right for Israel Railways to receive a 3% commission from consideration generated by smart-sensor sales agreements secured through Israel Railways.
That last detail matters more than it first appears. It shows that market entry still depends on a partner helping with access and commercialization, not on a mature shelf product already selling on its own. That is not a problem in itself. It is a sensible way to open a market. But it is another sign that the smart sensor still sits in the option-expansion stage, not in the proven revenue-engine stage.
There is another layer of caution. The company itself labels the smart-sensor program and the new HUMS development as forward-looking information that may fail because of market-entry difficulties, tender losses, defense-budget limits and competing products. So even in the section where management presents the vision, it does not hide the fact that commercialization still has to pass a real market test.
What Has To Happen For HUMS To Stop Being A Long-Dated Option
The first checkpoint is simple. The NIS 5.552 million that is scheduled for 2026 needs to hit the income statement, on time. Without that, the backlog remains mostly a headline.
The second checkpoint is quality, not just recognition. After a NIS 3.995 million gross loss and a NIS 7.199 million operating loss in 2025, more revenue alone is not enough. The segment needs to return to reasonable profitability. Otherwise the story becomes revenue without value.
The third checkpoint is commercialization in named orders, not just in the pipeline. The company already talks about fighter engines, UAVs and additional helicopter platforms. For the market to start reading HUMS as an engine, those talks have to become disclosed orders with timing that is closer than 2027 and beyond.
The fourth checkpoint is the smart sensor itself. If it is really supposed to expand the addressable market, the next stage cannot remain only grants and pilots. The company needs to show a repeat commercial order, or at least a clear move from pilot to paid deployment.
This is also where the post-balance-sheet order flow matters. In the first quarter of 2026 the company reported a series of orders, but most of the named ones were in control systems and MVR. Even the strategic March 24, 2026 order from Lockheed Martin was for development of a brake controller for a new aircraft. That is positive for the broader company picture, because it shows the ability to win new programs and strong anchor customers. But it is still not the signal investors are waiting to see inside HUMS itself.
Bottom Line
Arasal's HUMS backlog is real, but in 2025 it did not behave like an engine. It behaved like a long-dated option. The company has real proof of capability, certification, HAL adaptations, deliveries already completed, a smart-sensor roadmap backed by grants, and pilots across several markets. Those are meaningful assets.
But commercialization still has not converged into stable economics. Segment revenue collapsed, profitability flipped to loss, and most of the backlog moved into 2027 and beyond. The right read today is therefore not that HUMS has already become Arasal's future engine, but that it remains the company's most important long-term option, one with real technological substance, but also with a commercialization test that has not yet been passed.
In one line: HUMS has already proven it is a product, but it has not yet proven it is an engine.
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.