BIZTRAC BETA
Development of building projects

LEONORA EIENDOM AS

Org. no. 826346442 Limited company (AS) Bjørnafjorden Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 755,000
Operating profit NOK 455,000
Equity NOK 201,000
Incorporated 2020
Share capital NOK 30,000

LEONORA EIENDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 826346442. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling av fast eiendom, og det som står i forbindelse med dette, herunder å delta i andre selskap med slikt formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 755,000 in revenue and NOK 455,000 in operating profit.

Key figures · 2024

Revenue
NOK 755,000
Operating profit
NOK 455,000
Equity
NOK 201,000
Est. value
NOK 916,000

Financial health · 2024

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

Who owns LEONORA EIENDOM AS?

LEONORA HOLDING AS
LEONORA EIENDOM AS
NOK 755,000 rev. · NOK 455,000 profit

LEONORA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LEONORA EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about LEONORA EIENDOM AS

Who owns LEONORA EIENDOM AS?

LEONORA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LEONORA EIENDOM AS?

LEONORA EIENDOM AS had revenue of NOK 755,000 in 2024.

Who is the general manager of LEONORA EIENDOM AS?

Ellinor Hagen Petersen is registered as general manager of LEONORA EIENDOM AS.

Where is LEONORA EIENDOM AS based?

LEONORA EIENDOM AS has its business address in Lepsøy.

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.