BIZTRAC BETA
Other captive investment companies

MN HOLDING AS

Org. no. 914748291 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

MN HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 914748291. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikle, produsere og tilby operasjonelle og finansielle tjenester som fremmer elektrifisering av land og havgående transport og tjenester, og andre produkter og tjenester som naturlig faller sammen med dette, herunder delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 1.5m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns MN HOLDING AS?

EGIL MOLLESTAD
MN HOLDING AS
· NOK −5,000 profit

MN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MN HOLDING AS own?

MN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MN HOLDING AS

Who owns MN HOLDING AS?

EGIL MOLLESTAD is the largest registered owner, with 100.0%.

Who is the general manager of MN HOLDING AS?

Egil Mollestad is registered as general manager of MN HOLDING AS.

Where is MN HOLDING AS based?

MN HOLDING AS has its business address in Lysaker.

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.