biztrac. BETA
COMPANY REGISTER PROFILE
917995842 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MIVO INVEST AS

Org. no. 917995842 Limited company (AS) Ålesund Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 332,000
Incorporated 2016
Share capital NOK 132,000

Signals

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

MIVO INVEST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 917995842. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 132,000, divided into 131573 shares. The company's stated purpose is: “Kjøp, utvikling, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”.

Key figures · 2025

Operating profit
NOK −39,000
▲ +37 %
Equity
NOK 332,000
▲ +18 %
Est. value
NOK 303,000

Financial health · 2025

Liquidity
2.65
Very good
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
5.6%
Weak
Equity as a share of total capital

Who owns MIVO INVEST AS?

MIVO INVEST AS
· NOK −39,000 profit

MIVO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIVO INVEST AS own?

MIVO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MIVO INVEST AS er morselskap for 11 datterselskaper:

Frequently asked questions about MIVO INVEST AS

Who owns MIVO INVEST AS?

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

Who is the general manager of MIVO INVEST AS?

Martin Vidar Vollen is registered as general manager of MIVO INVEST AS.

Where is MIVO INVEST AS based?

MIVO INVEST AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.