BIZTRAC BETA
Rental and operating of own or leased real estate

M-O EIENDOM AS

Org. no. 829532522 Limited company (AS) Elverum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 918,000
Equity NOK −844,000
Incorporated 2022
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−844k kr).

M-O EIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 829532522. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investeringer og utleie av fast eiendom og annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 918,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 918,000
Equity
NOK −844,000
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns M-O EIENDOM AS?

M-O HOLDING AS
M-O EIENDOM AS
NOK 2.0m rev. · NOK 918,000 profit

M-O EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M-O EIENDOM AS

Who owns M-O EIENDOM AS?

M-O HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of M-O EIENDOM AS?

M-O EIENDOM AS had revenue of NOK 2.0m in 2025.

Who is the general manager of M-O EIENDOM AS?

Marius Olaussen is registered as general manager of M-O EIENDOM AS.

Where is M-O EIENDOM AS based?

M-O EIENDOM AS has its business address in Hernes.

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.