BIZTRAC BETA
Buying and selling of own real estate

MKB EIENDOM AS

Org. no. 997380622 Limited company (AS) Vefsn Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 1.6m
Equity NOK 2.9m
Incorporated 2011
Share capital NOK 100,000

MKB EIENDOM AS is registered as a limited company in Vefsn, Nordland with organisation number 997380622. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, utleie av anlegggsmidler, kjøp og salg av aksjer samt hva herunder står i forbindelse med, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 1.6m
Equity
NOK 2.9m
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.0%
Satisfactory
Equity as a share of total capital

Who owns MKB EIENDOM AS?

KENNETH BRÆKKEN
MKB EIENDOM AS
NOK 2.9m rev. · NOK 1.6m profit

MKB EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MKB EIENDOM AS own?

MKB EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MKB EIENDOM AS

Who owns MKB EIENDOM AS?

KENNETH BRÆKKEN is the largest registered owner, with 100.0%.

What is the revenue of MKB EIENDOM AS?

MKB EIENDOM AS had revenue of NOK 2.9m in 2025.

Who is the general manager of MKB EIENDOM AS?

Kenneth Brækken is registered as general manager of MKB EIENDOM AS.

Where is MKB EIENDOM AS based?

MKB EIENDOM AS has its business address in Mosjøen.

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.