BIZTRAC BETA
Buying and selling of own real estate

MBN EIENDOM AS

Org. no. 992583894 Limited company (AS) Flesberg Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −68,000
Equity NOK 2.0m
Incorporated 2008
Share capital NOK 150,000

Signals

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

MBN EIENDOM AS is registered as a limited company in Flesberg, Buskerud with organisation number 992583894. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 300 shares. The company's stated purpose is: “Drive eiendoms- og prosjektutvikling, kjøp, salg og drift av fast eiendom, deltakelse i andre selskaper ved aksjetegning eller på annen måte, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −68,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −68,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
30.95
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns MBN EIENDOM AS?

MESTERBYGG NUMEDAL AS
MBN EIENDOM AS
NOK 0 rev. · NOK −68,000 profit

MBN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MBN EIENDOM AS

Who owns MBN EIENDOM AS?

MESTERBYGG NUMEDAL AS is the largest registered owner, with 50.0%.

What is the revenue of MBN EIENDOM AS?

MBN EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of MBN EIENDOM AS?

Lars Simensen is registered as general manager of MBN EIENDOM AS.

Where is MBN EIENDOM AS based?

MBN EIENDOM AS has its business address in Svene.

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.