BIZTRAC BETA
Rental and operating of own or leased real estate

MOSANDEN EIENDOM AS

Org. no. 912867765 Limited company (AS) Trysil Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 576,000
Operating profit NOK 14,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 70,000

MOSANDEN EIENDOM AS is registered as a limited company in Trysil, Innlandet with organisation number 912867765. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Selskapets virksomhet er drift og forvaltning av fast eiendom, herunder kjøpt og salg av fast eiendom og investeringer i tilsvarende selskaper og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 576,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 576,000
Operating profit
NOK 14,000
Equity
NOK 1.1m
Est. value
NOK 794,000

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.5%
Good
Equity as a share of total capital

Who owns MOSANDEN EIENDOM AS?

EIRIK HALNES
MOSANDEN EIENDOM AS
NOK 576,000 rev. · NOK 14,000 profit

MOSANDEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOSANDEN EIENDOM AS

Who owns MOSANDEN EIENDOM AS?

EIRIK HALNES is the largest registered owner, with 50.0%.

What is the revenue of MOSANDEN EIENDOM AS?

MOSANDEN EIENDOM AS had revenue of NOK 576,000 in 2024.

Who is the general manager of MOSANDEN EIENDOM AS?

Eirik Halnes is registered as general manager of MOSANDEN EIENDOM AS.

Where is MOSANDEN EIENDOM AS based?

MOSANDEN EIENDOM AS has its business address in Trysil.

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.