BIZTRAC BETA
Business and other management consultancy activities

MARINUTRA AS

Org. no. 997116909 Limited company (AS) Ålesund Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 219,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

MARINUTRA AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 997116909. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rådgivning innen industriell virksomhet, management og andre aktiviteter som forventes å gi økonomisk avkastning, enten direkte eller ved kjøp av aksjer, parter eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 219,000
Est. value
NOK 356,000

Financial health · 2024

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

Who owns MARINUTRA AS?

BJØRN REFSUM
MARINUTRA AS
NOK 0 rev. · NOK −18,000 profit

MARINUTRA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARINUTRA AS

Who owns MARINUTRA AS?

BJØRN REFSUM is the largest registered owner, with 100.0%.

What is the revenue of MARINUTRA AS?

MARINUTRA AS had revenue of NOK 0 in 2024.

Who is the general manager of MARINUTRA AS?

Bjørn Refsum is registered as general manager of MARINUTRA AS.

Where is MARINUTRA AS based?

MARINUTRA AS has its business address in Ålesund.

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.