BIZTRAC BETA
Wholesale of other machinery and equipment

MARICULTURE AS

Org. no. 918035893 Limited company (AS) Frøya Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −884,000
Equity NOK 275.9m
Incorporated 2016
Share capital NOK 570,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−884k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MARICULTURE AS is registered as a limited company in Frøya, Trøndelag with organisation number 918035893. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2016. Registered share capital is NOK 570,000, divided into 300 shares. The company's stated purpose is: “Å drive med utvikling, salg, utleie og service av oppdrettsanlegg inklusive systemer og utstyr, eie og investere i aksjer og andre selskaper og virksomheter, samt deltakelse av enhver art i andre forretningsforetagende, kjøp og salg av fast eiendom og hva dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −884,000
Equity
NOK 275.9m
Est. value
NOK 344.9m

Financial health · 2024

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

Who owns MARICULTURE AS?

SALMAR OCEAN AS
MARICULTURE AS
· NOK −884,000 profit

MARICULTURE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARICULTURE AS

Who owns MARICULTURE AS?

SALMAR OCEAN AS is the largest registered owner, with 100.0%.

Who is the general manager of MARICULTURE AS?

Anders Jon Fjellheim is registered as general manager of MARICULTURE AS.

Where is MARICULTURE AS based?

MARICULTURE AS has its business address in Kverva.

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.