BIZTRAC BETA
Rental and operating of own or leased real estate

LYGRE EIENDOM AS

Org. no. 885558542 Limited company (AS) Bjørnafjorden Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 707,000
Operating profit NOK 123,000
Equity NOK 59,000
Incorporated 2003
Share capital NOK 100,000

LYGRE EIENDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 885558542. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og utleie og alt hva dermed er forbundet, deriblant deltakelse og investering i annen virksomhet og andre selskaper i inn- og utland.”. The most recent filed accounts, for the 2025 financial year, show NOK 707,000 in revenue and NOK 123,000 in operating profit.

Key figures · 2025

Revenue
NOK 707,000
Operating profit
NOK 123,000
Equity
NOK 59,000
Est. value
NOK 225,000

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

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

Who owns LYGRE EIENDOM AS?

ÅGE LYGRE
LYGRE EIENDOM AS
NOK 707,000 rev. · NOK 123,000 profit

LYGRE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYGRE EIENDOM AS own?

LYGRE EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYGRE EIENDOM AS

Who owns LYGRE EIENDOM AS?

ÅGE LYGRE is the largest registered owner, with 100.0%.

What is the revenue of LYGRE EIENDOM AS?

LYGRE EIENDOM AS had revenue of NOK 707,000 in 2025.

Where is LYGRE EIENDOM AS based?

LYGRE EIENDOM AS has its business address in Eikelandsosen.

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.