BIZTRAC BETA
Rental and operating of own or leased real estate

MIVA EIENDOM AS

Org. no. 918746382 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −43,000
Equity NOK 5.6m
Incorporated 2017
Share capital NOK 100,000

Signals

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

MIVA EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 918746382. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, oppføring og utleie av eiendommer, herunder deltakelse i andre selskap, samt virksomhet som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −43,000
Equity
NOK 5.6m
Est. value
NOK 4.1m

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.7%
Very good
Equity as a share of total capital

Who owns MIVA EIENDOM AS?

MIKAEL JACOBSEN VANG
MIVA EIENDOM AS
NOK 3,000 rev. · NOK −43,000 profit

MIVA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIVA EIENDOM AS own?

MIVA EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MIVA EIENDOM AS

Who owns MIVA EIENDOM AS?

MIKAEL JACOBSEN VANG is the largest registered owner, with 100.0%.

What is the revenue of MIVA EIENDOM AS?

MIVA EIENDOM AS had revenue of NOK 3,000 in 2024.

Where is MIVA EIENDOM AS based?

MIVA EIENDOM AS has its business address in Bergen.

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.