BIZTRAC BETA
Rental and operating of own or leased real estate

LEGENE DANHOLMEN 3 AS

Org. no. 993028762 Limited company (AS) Færder Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 810,000
Operating profit NOK 485,000
Equity NOK 1.4m
Incorporated 2008
Share capital NOK 100,000

LEGENE DANHOLMEN 3 AS is registered as a limited company in Færder, Vestfold with organisation number 993028762. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendommer, aksjer, verdipapirer og hva som dermed står i forbindelse, herunder også deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 810,000 in revenue and NOK 485,000 in operating profit.

Key figures · 2025

Revenue
NOK 810,000
Operating profit
NOK 485,000
Equity
NOK 1.4m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
24.03
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.2%
Good
Equity as a share of total capital

Who owns LEGENE DANHOLMEN 3 AS?

TSCHUDI EIENDOM AS
LEGENE DANHOLMEN 3 AS
NOK 810,000 rev. · NOK 485,000 profit

LEGENE DANHOLMEN 3 AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEGENE DANHOLMEN 3 AS

Who owns LEGENE DANHOLMEN 3 AS?

TSCHUDI EIENDOM AS is the largest registered owner, with 40.0%.

What is the revenue of LEGENE DANHOLMEN 3 AS?

LEGENE DANHOLMEN 3 AS had revenue of NOK 810,000 in 2025.

Who is the general manager of LEGENE DANHOLMEN 3 AS?

Helge Magnus Larsen is registered as general manager of LEGENE DANHOLMEN 3 AS.

Where is LEGENE DANHOLMEN 3 AS based?

LEGENE DANHOLMEN 3 AS has its business address in Nøtterø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.