BIZTRAC BETA
Rental and operating of own or leased real estate

MYKLERUDVEIEN EIENDOM AS

Org. no. 924701382 Limited company (AS) Nesodden Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −55,000
Equity NOK −1.8m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).

MYKLERUDVEIEN EIENDOM AS is registered as a limited company in Nesodden, Akershus with organisation number 924701382. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av eiendom, eiendomsutvikling og eiendomsdrift i Norge gjennom egeneide eiendommer samt hel- og deleide selskaper.”.

Key figures · 2024

Operating profit
NOK −55,000
Equity
NOK −1.8m

Financial health · 2024

Liquidity
3.95
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.0%
Weak
Equity as a share of total capital

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

Who owns MYKLERUDVEIEN EIENDOM AS?

DNW HOLDING AS
MYKLERUDVEIEN EIENDOM AS
· NOK −55,000 profit

MYKLERUDVEIEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MYKLERUDVEIEN EIENDOM AS own?

MYKLERUDVEIEN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MYKLERUDVEIEN EIENDOM AS er morselskap for 4 datterselskaper:

Frequently asked questions about MYKLERUDVEIEN EIENDOM AS

Who owns MYKLERUDVEIEN EIENDOM AS?

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

Where is MYKLERUDVEIEN EIENDOM AS based?

MYKLERUDVEIEN EIENDOM AS has its business address in Fagerstrand.

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.