BIZTRAC BETA
Manufacture of beer

LENDING GARD AS

Org. no. 921270852 Limited company (AS) Fjaler Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 201,000
Operating profit NOK 5,000
Equity NOK −230,000
Incorporated 2018
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−230k kr).

LENDING GARD AS is registered as a limited company in Fjaler, Vestland with organisation number 921270852. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2018. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Produksjon av økologisk brus, øl og alkoholhaldig drikke, med dertil tilhøyrande virksomheit. Leverandør av økologiske råvarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 201,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 201,000
Operating profit
NOK 5,000
Equity
NOK −230,000
Est. value
NOK 44,000

Financial health · 2025

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-236.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LENDING GARD AS?

LEIF JARLE ESPEDAL
LENDING GARD AS
NOK 201,000 rev. · NOK 5,000 profit

LENDING GARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LENDING GARD AS

Who owns LENDING GARD AS?

LEIF JARLE ESPEDAL is the largest registered owner, with 100.0%.

What is the revenue of LENDING GARD AS?

LENDING GARD AS had revenue of NOK 201,000 in 2025.

Who is the general manager of LENDING GARD AS?

Leif Jarle Espedal is registered as general manager of LENDING GARD AS.

Where is LENDING GARD AS based?

LENDING GARD AS has its business address in Flekke.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.