BIZTRAC BETA
COMPANY REGISTER PROFILE
959129118 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

MAMA ROSA EIENDOM AS

Org. no. 959129118 Limited company (AS) Midtre Gauldal Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 871,000
Operating profit NOK 392,000
Equity NOK 347,000
Incorporated 1990
Share capital NOK 71,000

MAMA ROSA EIENDOM AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 959129118. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 71,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av fast eiendom, handel og investeringsvirksomhet samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 871,000 in revenue and NOK 392,000 in operating profit.

Former names: ARGUM AS, STØRENS BAGERI AS

Key figures · 2025

Revenue
NOK 871,000
▲ +34 %
Operating profit
NOK 392,000
▲ +4 %
Equity
NOK 347,000
▼ −52 %
Est. value
NOK 826,000

Financial health · 2025

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
15.4%
Very good
Return on total assets
Solidity
6.7%
Weak
Equity as a share of total capital

Who owns MAMA ROSA EIENDOM AS?

MAMA ROSA EIENDOM AS
NOK 871,000 rev. · NOK 392,000 profit

MAMA ROSA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAMA ROSA EIENDOM AS

Who owns MAMA ROSA EIENDOM AS?

MAMA ROSA STØREN AS is the largest registered owner, with 100.0%.

What is the revenue of MAMA ROSA EIENDOM AS?

MAMA ROSA EIENDOM AS had revenue of NOK 871,000 in 2025.

Where is MAMA ROSA EIENDOM AS based?

MAMA ROSA EIENDOM AS has its business address in Støren.

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

Report a problem

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