BIZTRAC BETA
Development of building projects

MSH EIENDOM AS

Org. no. 927260662 Limited company (AS) Halden Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 1.1m
Equity NOK 1.3m
Incorporated 2021
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MSH EIENDOM AS is registered as a limited company in Halden, Østfold with organisation number 927260662. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utvikling, eie og drift av fast eiendom, kjøp og salg av fast eiendom, kjøp og salg av aksjer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 1.1m
Equity
NOK 1.3m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns MSH EIENDOM AS?

MSH UTVIKLING AS
MSH EIENDOM AS
NOK 2.1m rev. · NOK 1.1m profit

MSH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MSH EIENDOM AS

Who owns MSH EIENDOM AS?

MSH UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of MSH EIENDOM AS?

MSH EIENDOM AS had revenue of NOK 2.1m in 2024.

Who is the general manager of MSH EIENDOM AS?

Jan Roger Eriksen is registered as general manager of MSH EIENDOM AS.

Where is MSH EIENDOM AS based?

MSH EIENDOM AS has its business address in Halden.

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.