BIZTRAC BETA
Rental and operating of own or leased real estate

MOG EIENDOM AS

Org. no. 994385976 Limited company (AS) Surnadal Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 408,000
Equity NOK 1.7m
Incorporated 2009
Share capital NOK 100,000

MOG EIENDOM AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 994385976. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 408,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 408,000
Equity
NOK 1.7m
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns MOG EIENDOM AS?

MNO HOLDING AS
MOG EIENDOM AS
NOK 1.5m rev. · NOK 408,000 profit

MOG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOG EIENDOM AS

Who owns MOG EIENDOM AS?

MNO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MOG EIENDOM AS?

MOG EIENDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of MOG EIENDOM AS?

Rune Mogstad is registered as general manager of MOG EIENDOM AS.

Where is MOG EIENDOM AS based?

MOG EIENDOM AS has its business address in Surnadal.

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.