BIZTRAC BETA
Support activities for fishing and aquaculture

NESSA OPPDRETTSMILJØ AS

Org. no. 932910195 Limited company (AS) Hjelmeland Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 392,000
Equity NOK 558,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-22 Adresseendring registrert 2026-02-22.

NESSA OPPDRETTSMILJØ AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 932910195. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selge service tjenester rettet mot havbruk/fiskeoppdrett.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 392,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 392,000
Equity
NOK 558,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns NESSA OPPDRETTSMILJØ AS?

NESSA SJØFRAKT AS
NESSA OPPDRETTSMILJØ AS
NOK 1.2m rev. · NOK 392,000 profit

NESSA OPPDRETTSMILJØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NESSA OPPDRETTSMILJØ AS

Who owns NESSA OPPDRETTSMILJØ AS?

NESSA SJØFRAKT AS is the largest registered owner, with 50.0%.

What is the revenue of NESSA OPPDRETTSMILJØ AS?

NESSA OPPDRETTSMILJØ AS had revenue of NOK 1.2m in 2024.

Who is the general manager of NESSA OPPDRETTSMILJØ AS?

Ole Bjørn Nessa is registered as general manager of NESSA OPPDRETTSMILJØ AS.

Where is NESSA OPPDRETTSMILJØ AS based?

NESSA OPPDRETTSMILJØ AS has its business address in Fister.

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.