BIZTRAC BETA
Rental and operating of own or leased real estate

M. A. EIENDOM AS

Org. no. 986205217 Limited company (AS) Drammen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 483,000
Equity NOK 7.7m
Incorporated 2003
Share capital NOK 100,000

M. A. EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 986205217. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsselskap med kjøp/salg, utleie og utvikling av fast eiendom, hotelldrift og dertil virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 483,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 483,000
Equity
NOK 7.7m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns M. A. EIENDOM AS?

MOHAMMAD ANSAR
M. A. EIENDOM AS
NOK 2.0m rev. · NOK 483,000 profit

M. A. EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M. A. EIENDOM AS own?

M. A. EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M. A. EIENDOM AS

Who owns M. A. EIENDOM AS?

MOHAMMAD ANSAR is the largest registered owner, with 100.0%.

What is the revenue of M. A. EIENDOM AS?

M. A. EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of M. A. EIENDOM AS?

Mohammad Ansar is registered as general manager of M. A. EIENDOM AS.

Where is M. A. EIENDOM AS based?

M. A. EIENDOM AS has its business address in Mjøndalen.

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.