BIZTRAC BETA
Development of building projects

M3-EIENDOM AS

Org. no. 916993919 Limited company (AS) Lunner Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 992,000
Incorporated 2016
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

M3-EIENDOM AS is registered as a limited company in Lunner, Akershus with organisation number 916993919. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 150 shares. The company's stated purpose is: “Drive utvikling og salg av eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 992,000
Est. value
NOK 905,000

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.4%
Very good
Equity as a share of total capital

Who owns M3-EIENDOM AS?

BJØRN ATLE RUUD
M3-EIENDOM AS
NOK 0 rev. · NOK −29,000 profit

M3-EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about M3-EIENDOM AS

Who owns M3-EIENDOM AS?

BJØRN ATLE RUUD is the largest registered owner, with 33.3%.

What is the revenue of M3-EIENDOM AS?

M3-EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of M3-EIENDOM AS?

Aleksander Dehlimarken is registered as general manager of M3-EIENDOM AS.

Where is M3-EIENDOM AS based?

M3-EIENDOM AS has its business address in Grua.

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.