BIZTRAC BETA
Support activities for fishing and aquaculture

HAVNEFRUEN AS

Org. no. 918448357 Limited company (AS) Moss Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 195,000
Operating profit NOK 1,000
Equity NOK 45,000
Incorporated 2017
Share capital NOK 30,000

HAVNEFRUEN AS is registered as a limited company in Moss, Østfold with organisation number 918448357. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Yte tjenester innen akvakultur, samt annen virksomhet som drift og vedlikehold av fast eiendom, havneanlegg og båter. Selskapet kan drive agentur- og handelsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 195,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 195,000
Operating profit
NOK 1,000
Equity
NOK 45,000
Est. value
NOK 26,000

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAVNEFRUEN AS?

GUNN BERIT RODAL
HAVNEFRUEN AS
NOK 195,000 rev. · NOK 1,000 profit

HAVNEFRUEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVNEFRUEN AS

Who owns HAVNEFRUEN AS?

GUNN BERIT RODAL is the largest registered owner, with 100.0%.

What is the revenue of HAVNEFRUEN AS?

HAVNEFRUEN AS had revenue of NOK 195,000 in 2025.

Who is the general manager of HAVNEFRUEN AS?

Gunn Berit Rodal is registered as general manager of HAVNEFRUEN AS.

Where is HAVNEFRUEN AS based?

HAVNEFRUEN AS has its business address in Moss.

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.