BIZTRAC BETA
Other technical consultancy

F.M INVEST AS

Org. no. 995566222 Limited company (AS) Lørenskog Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −84,000
Equity NOK 39.9m
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−84k kr).
  • Nylig endring 2026-02-04 Adresseendring registrert 2026-02-04.

F.M INVEST AS is registered as a limited company in Lørenskog, Akershus with organisation number 995566222. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulent virksomhet innen miljøteknisk rådgivning,salg og operativ utførelse 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”.

Key figures · 2024

Operating profit
NOK −84,000
Equity
NOK 39.9m
Est. value
NOK 387.0m

Financial health · 2024

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

Who owns F.M INVEST AS?

FRED YTTERDAHL
F.M INVEST AS
· NOK −84,000 profit

F.M INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does F.M INVEST AS own?

F.M INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about F.M INVEST AS

Who owns F.M INVEST AS?

FRED YTTERDAHL is the largest registered owner, with 80.0%.

Who is the general manager of F.M INVEST AS?

Fred Ytterdahl is registered as general manager of F.M INVEST AS.

Where is F.M INVEST AS based?

F.M INVEST AS has its business address in Lørenskog.

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.