BIZTRAC BETA
Rental and operating of own or leased real estate

MP EIENDOMSINVEST AS

Org. no. 926765817 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 387,000
Operating profit NOK 91,000
Equity NOK 282,000
Incorporated 2021
Share capital NOK 100,000

MP EIENDOMSINVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 926765817. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i, utvikling, drift og utleie av fast eiendom, samt investeringer i andre selskaper og dertil naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 387,000 in revenue and NOK 91,000 in operating profit.

Key figures · 2025

Revenue
NOK 387,000
Operating profit
NOK 91,000
Equity
NOK 282,000
Est. value
NOK 348,000

Financial health · 2024

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

Who owns MP EIENDOMSINVEST AS?

KAPTEIN1 INVEST AS
MP EIENDOMSINVEST AS
NOK 387,000 rev. · NOK 91,000 profit

MP EIENDOMSINVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MP EIENDOMSINVEST AS own?

MP EIENDOMSINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MP EIENDOMSINVEST AS

Who owns MP EIENDOMSINVEST AS?

KAPTEIN1 INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of MP EIENDOMSINVEST AS?

MP EIENDOMSINVEST AS had revenue of NOK 387,000 in 2025.

Where is MP EIENDOMSINVEST AS based?

MP EIENDOMSINVEST AS has its business address in Svelvik.

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.