BIZTRAC BETA
Other captive investment companies

FLOW M AS

Org. no. 980601706 Limited company (AS) Herøy Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −97,000
Equity NOK 3.7m
Incorporated 1998
Share capital NOK 605,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−97k kr).

FLOW M AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 980601706. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1998. Registered share capital is NOK 605,000, divided into 6048 shares. The company's stated purpose is: “Kjøp og salg av maritime varer og tjenester, ta del i selskap med lignende formål, samt eige, kjøpe og selge aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −97,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −97,000
Equity
NOK 3.7m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns FLOW M AS?

ROGER MYKLEBUSTHAUG
FLOW M AS
NOK 0 rev. · NOK −97,000 profit

FLOW M AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FLOW M AS own?

FLOW M AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about FLOW M AS

Who owns FLOW M AS?

ROGER MYKLEBUSTHAUG is the largest registered owner, with 33.3%.

What is the revenue of FLOW M AS?

FLOW M AS had revenue of NOK 0 in 2024.

Who is the general manager of FLOW M AS?

Roger Myklebusthaug is registered as general manager of FLOW M AS.

Where is FLOW M AS based?

FLOW M AS has its business address in Fosnavåg.

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.