Av-Gad's Debt Layer: Project Surplus Is the Core Liquidity Source
Av-Gad is not currently presenting as a near-term covenant breach story, but its liquidity forecast depends heavily on project surplus released after Series B and C repayments. That makes the timing of releases from project accounts the key test for the debt layer.
The main article on Av-Gad argued that the first quarter restored gross profit before the projects released enough cash to support the funding structure. This continuation isolates the debt layer, and the read is sharper: the current risk does not look like an immediate covenant breach, but rather a dependence on when project surplus moves from project-control accounts to the company. The board reviewed cash of NIS 15.9 million against much larger expected expenses, investments and liabilities, and the largest liquidity source in that review is NIS 787.8 million of project surplus after repayment of Series B and C bonds. The size of the backlog or the sales pace is therefore not enough. The relevant path is how surplus is released, from which projects, after which debt repayments, and at what speed relative to finance costs. The main constraint is that this surplus is not free cash already sitting at the parent: it depends on project financing, banks, construction pace, deliveries, sales and collateral arrangements for bondholders. The next proof points are actual surplus release, the near Series B repayments, and covenant room maintained without adding another expensive debt layer.
Liquidity Depends On Surplus, Not Cash On Hand
The liquidity starting point is modest relative to the size of the activity. Cash at the end of March 2026 was NIS 15.9 million, after negative operating cash flow of NIS 53.5 million in the quarter. Positive investing cash flow of NIS 15.2 million and positive financing cash flow of NIS 20.1 million reduced the cash decline, but did not eliminate it. In practical terms, the quarter already showed a larger operating base, while still requiring net funding to bridge construction, revenue recognition and collection.
The most important number in the company's liquidity review is not the cash balance itself. The board reviewed expected expenses and investments of NIS 830.7 million, current liabilities of NIS 430.6 million and non-current liabilities of NIS 226.3 million. Against these items, it pointed to planned new bond issuances, existing credit facilities of NIS 70.7 million, alternative financing proposals, potential project partners, and primarily project surplus of NIS 787.8 million to be released after Series B and C bond repayments.
| Layer Reviewed | Amount | Liquidity Meaning |
|---|---|---|
| Cash at the end of March 2026 | NIS 15.9 million | Available source, but small relative to operating needs |
| Existing credit facilities | NIS 70.7 million | Supplemental funding layer, not the main source |
| Project surplus after Series B and C repayment | NIS 787.8 million | The largest source in the forecast, and therefore the main dependency |
This is a very different layer from free cash. Project surplus arrives only after enough milestones are cleared: project finance, investment, sales, construction progress, buyer payments and approval to release money from project accounts. For an urban-renewal developer, that is part of the normal model. What is decisive at Av-Gad is the weight the company places on those surpluses relative to cash on hand and the debt structure. When the main liquidity source is future project surplus, every delay in a project or in the release mechanism can quickly become a higher financing cost.
The Debt Gives Bondholders Priority Before Equity Holders
The bond layer does not currently look like an imminent breach point. The company is in compliance with the financial covenants of Series B, C and D. Equity was NIS 128.5 million, above the NIS 40 million threshold for Series B and the NIS 50 million threshold for Series C and D. The collateral-to-debt ratio was about 205% for Series B versus a 125% minimum, and about 136% for Series C versus the same threshold. Net financial debt to net CAP was about 71%, versus an 85% ceiling for Series C and D. The liquidity requirement for the next interest payment also looks comfortably covered: liquid balances of NIS 15.9 million versus upcoming interest payments of NIS 1.3 million for Series B and NIS 3.8 million for Series C.
That does not make the debt comfortable. Series B and C are secured by project-surplus pledges, while Series D is unsecured. The three series are unlinked and carry fixed annual coupons of 9.5%, 7.2% and 6.8%, respectively. Their carrying amounts at the end of March were NIS 27.2 million for Series B, NIS 105.7 million for Series C and NIS 91.6 million for Series D. Series B also has nearer repayments: 20% of principal on June 30, 2026, 25% on December 31, 2026 and another 20% on June 30, 2027.
This is where project surplus and debt connect. Surplus from projects pledged to Series B and C does not flow directly to the equity layer. It first serves the collateral and repayment structure. Even when the liquidity forecast includes a large surplus number, the economic order matters: bondholders have priority, and the company has to prove that the projects release enough money after that priority is met.
Cross-Default Turns A Local Delay Into A Wider Risk
The covenants are far enough from breach that this should not be written as an immediate default story. The cross-default disclosure is why the analysis should not stop there. If one series is accelerated, it can create acceleration grounds for other series. If Series B is accelerated, it may trigger NIS 197.3 million of Series C and D debt. If Series C is accelerated, the parallel amount against Series B and D is about NIS 118.8 million. If Series D is accelerated, the parallel amount against Series B and C is about NIS 132.9 million.
That linkage also exists in project financing. The cross-default table names financing bodies across projects such as Golomb 5, Hankin 17, HaHayil, Golomb 38 and HaGeonim. Acceleration in one of them can create grounds against the bonds and against other financing agreements. This is not a forecast that such an event will occur. It is a description of a sensitive structure: a specific problem in one financed project can spread faster when debt, collateral and project-control accounts are tied together.
One event during the reporting period sharpens this point without changing the main thesis. In the Tselah project in Petah Tikva, the company received 62.5% of the project company, while required equity is estimated at about NIS 18.6 million and the third party's share is about NIS 4 million. The company committed to provide the remaining equity required for that party as a loan. The amount is small relative to the debt layer, but it is a useful reminder that project growth can require the company to finance not only its own equity share, but also temporary support for partners before surplus is released.
The Read Changes Only When Surplus Reaches The Company
The current read of Av-Gad's debt is mixed with a clear lean: there is no immediate covenant-breach signal, but liquidity depends on a source that arrives later in the project life cycle. If project surplus is released at a pace that matches near repayments and finance costs, the debt structure will look like a reasonable bridge for a growing backlog. If release is delayed, the company remains more dependent on new debt issuance, credit facilities and partner capital, while finance costs are already consuming a large part of operating profit. The next report needs to show not only more sales or more backlog, but reduced dependence on external funding through cash released from project accounts after debt repayments.
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.