Gilat Telecom: How Much of 2026 Really Depends on One Israeli Customer and Non-Binding Frameworks
Gilat's early-2026 Israeli order wave is real, but it is more concentrated and less firm than the roughly NIS 110 million headline suggests. About two-thirds of the disclosed amount in this follow-up sits in one repeatedly enlarged customer thread, while part of the headline still depends on framework usage that was not yet committed at filing date.
What This Follow-Up Is Isolating
The main article already argued that the early-2026 order wave is central to the 2026 thesis. This follow-up isolates a narrower question: how much of that wave is genuinely broad demand, and how much is really one Israeli customer expanding the same engagement again and again, plus framework language that still depends on actual drawdown.
That matters because management itself folded this sequence of notices into its liquidity and forward-visibility argument. In the annual report's board discussion, the company groups the Israeli notice flow into a roughly NIS 110 million headline for the coming year. But once the filings are unpacked, it becomes clear that not every shekel inside that headline carries the same economic quality.
Across the selected notices used here, the disclosed amounts add up to roughly NIS 109.4 million. That sits very close to the annual report's roughly NIS 110 million framing, but the underlying mix is far from uniform: one thread alone reaches NIS 73.5 million, a second thread reaches NIS 14.3 million, one NIS 6.9 million framework is only partly firm, and the remaining February-March notices are much smaller. Demand is there. Diversification is less impressive.
The chart above uses the amounts exactly as disclosed in each notice. That is not a technical footnote. It is part of the analytical read: the 9 March notice was disclosed excluding VAT, while most of the other notices were disclosed including VAT. So the roughly NIS 110 million headline is a good indication of scale, but not a clean stand-alone measure of quality.
Where The Concentration Actually Sits
This is the core point. The notices from 30 January, 6 February and 19 February are not three separate wins. They are one thread. Each notice explicitly points back to the earlier one and lifts the same Israeli customer engagement from NIS 52 million, to NIS 58 million, to NIS 62 million, and finally to NIS 73.5 million. All of them relate to the current year.
That leads to the main conclusion: even before trying to guess whether some of the other notices may involve the same customer, the filings already show one thread accounting for roughly two-thirds of the disclosed wave examined here. This is not equal-sized demand spread across several customers. It is high dependence on one customer, or at least on one annual engagement, that keeps getting upsized.
The 1 January and 28 January thread is also not two independent wins. On 1 January the company disclosed an order of about NIS 5 million for 12 months, with room to grow. By 28 January the same thread had been updated to NIS 14.3 million for the same period. That is real demand, but not proof of breadth. At most, it shows that Gilat managed to expand an existing engagement very quickly.
The important point is what cannot be said. The filings do not disclose whether the NIS 14.3 million thread is the same customer as the NIS 73.5 million thread or a different one. So any reading that presents the whole wave as proof of broad diversification goes too far. What can be said with confidence is that a very large part of the wave comes from repeated enlargements around a customer already inside the base.
| Thread | Anchor files | Current amount | What the filings actually prove |
|---|---|---|---|
| Main enlargement thread | 30 Jan, 6 Feb, 19 Feb | NIS 73.5 m | Same customer, same year, same thread repeatedly enlarged |
| January thread | 1 Jan, 28 Jan | NIS 14.3 m | Same 2026 engagement scaled up quickly, with no disclosure linking it to the main thread |
| 20 February framework | 20 Feb | NIS 6.9 m | One headline where not all of the amount was firm at filing date |
| Additional notices | 24 Feb, 5 Mar, 9 Mar | NIS 14.7 m | Separate notices that add some breadth, but remain much smaller than the NIS 73.5 m thread |
How Much of the NIS 6.9 Million Is Truly Committed
The 20 February notice has a very different economic quality from the rest of the wave. This is not just another service order. The company itself splits the deal into two components: about NIS 2.5 million of equipment that is binding, and a services component that makes up the balance under a non-binding 2026 framework. Beyond that, the customer had only notified about NIS 350 thousand of service usage at filing date.
In other words, out of the NIS 6.9 million headline, only NIS 2.5 million of binding equipment plus NIS 350 thousand of already-notified service usage were concrete at that point. Roughly NIS 4.05 million still depended on the customer actually consuming the service during the year. That is not the same backlog quality.
The analytical takeaway is straightforward. If the NIS 6.9 million headline is read as if it were fully equivalent to a firm signed 2026 order, the visibility read becomes too optimistic. A better read is that the notice contains both a firm piece and an option-like piece. That is still positive, because the customer is already active and the equipment component is binding, but it is not the same as a fully locked-in NIS 6.9 million order.
What Can Still Be Said About Demand Breadth
The notices from 24 February, 5 March and 9 March do add a genuine layer of demand beyond the two enlargement threads. They are also not presented as follow-on enlargements of earlier notices, so at the filing level they do look like additional demand points rather than another chapter in the same thread.
But the scale still matters. Together they amount to NIS 14.7 million on their original disclosure bases, versus NIS 73.5 million in the main enlargement thread. One of them also runs until November 2027, so it should not be read as if all of its value were equivalent to revenue falling cleanly into 2026. There is some breadth here, but not enough to erase the fact that the heavy mass of the wave still sits with one dominant customer thread.
That distinction also matters because management uses the notice sequence to support a broader argument about backlog quality, cash visibility and liquidity. Once the whole sequence is asked to carry that burden, readers need to separate three things: orders already signed for 2026, repeat enlargements concentrated in one customer, and framework notices that still need to turn into actual usage.
Bottom Line
This follow-up does not overturn the constructive message in the main article. It sharpens it. The Israeli order wave at the start of 2026 is real, and it does support the view that the domestic activity entered the year with business momentum. But it does not look like six independent, equal-weight wins. It looks like one very large NIS 73.5 million thread, one smaller NIS 14.3 million thread, a handful of additional orders at more modest size, and one framework where a meaningful part was still not firm.
So the right read of 2026 is not "roughly NIS 110 million of new, diversified Israeli demand." The better read is "a meaningful order wave whose quality depends heavily on one customer and on the conversion of frameworks and follow-on notices into actual revenue." If the coming quarters show that the NIS 73.5 million thread is indeed translating into revenue and collections at a stable pace, that concern will fade. If not, concentration remains the main yellow flag underneath the impressive headline flow.
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.