BIZTRAC BETA
Rental and operating of own or leased real estate

MM TUSTNA AS

Org. no. 932000709 Limited company (AS) Aure Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

MM TUSTNA AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 932000709. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikle 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 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 18,000
Est. value
NOK 16,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

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

Who owns MM TUSTNA AS?

DAG RUNE MYRMEL
MM TUSTNA AS
NOK 0 rev. · NOK −5,000 profit

MM TUSTNA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MM TUSTNA AS

Who owns MM TUSTNA AS?

DAG RUNE MYRMEL is the largest registered owner, with 33.3%.

What is the revenue of MM TUSTNA AS?

MM TUSTNA AS had revenue of NOK 0 in 2025.

Where is MM TUSTNA AS based?

MM TUSTNA AS has its business address in Tustna.

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.