biztrac. BETA
COMPANY REGISTER PROFILE
826324422 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

M&G EIENDOM AS

Org. no. 826324422 Limited company (AS) Moss Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −174,000
Equity NOK 2.2m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−174k kr).

M&G EIENDOM AS is registered as a limited company in Moss, Østfold with organisation number 826324422. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring og salg av eiendom samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −174,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −174,000
▼ −8 %
Equity
NOK 2.2m
▼ −6 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
63.38
Very good
Current assets ÷ current liabilities
Profitability
-2.0%
Not satisfactory
Return on total assets
Solidity
34.3%
Good
Equity as a share of total capital

Who owns M&G EIENDOM AS?

M&G EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about M&G EIENDOM AS

Who owns M&G EIENDOM AS?

MEMO CAPITAL AS is the largest registered owner, with 40.0%.

What is the revenue of M&G EIENDOM AS?

M&G EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of M&G EIENDOM AS?

Ronny Gundersen is registered as general manager of M&G EIENDOM AS.

Where is M&G EIENDOM AS based?

M&G EIENDOM AS has its business address in Dilling.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.