BIZTRAC BETA
Uoppgitt

MMT INVEST AS

Org. no. 924692383 Limited company (AS) Østre Toten Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −34,000
Equity NOK 38.4m
Incorporated 2019
Share capital NOK 150,000

Signals

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

MMT INVEST AS is registered as a limited company in Østre Toten, Innlandet with organisation number 924692383. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 150,000, divided into 15 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −34,000
Equity
NOK 38.4m
Est. value
NOK 41.5m

Financial health · 2025

Liquidity
5.51
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.5%
Very good
Equity as a share of total capital

Who owns MMT INVEST AS?

METTE MARTINSEN TARALRUD
MMT INVEST AS
NOK 3,000 rev. · NOK −34,000 profit

MMT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MMT INVEST AS own?

MMT INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MMT INVEST AS

Who owns MMT INVEST AS?

METTE MARTINSEN TARALRUD is the largest registered owner, with 100.0%.

What is the revenue of MMT INVEST AS?

MMT INVEST AS had revenue of NOK 3,000 in 2025.

Where is MMT INVEST AS based?

MMT INVEST AS has its business address in Kapp.

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.