BIZTRAC BETA
Marine fishing

MS HAUGEN AS

Org. no. 986558721 Limited company (AS) Vanylven Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK −816,000
Equity NOK −1.2m
Incorporated 2003
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−816k kr).

MS HAUGEN AS is registered as a limited company in Vanylven, Møre og Romsdal with organisation number 986558721. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Næringsvirksomhet innen fiskeri, herunder deltagelse i og/eller investering i andre selskaper, og alt hva dermed er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK −816,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK −816,000
Equity
NOK −1.2m

Financial health · 2024

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.7%
Weak
Equity as a share of total capital

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

Who owns MS HAUGEN AS?

JOHNNY ALMKLOV HAUGEN
MS HAUGEN AS
NOK 4.7m rev. · NOK −816,000 profit

MS HAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MS HAUGEN AS own?

MS HAUGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MS HAUGEN AS

Who owns MS HAUGEN AS?

JOHNNY ALMKLOV HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of MS HAUGEN AS?

MS HAUGEN AS had revenue of NOK 4.7m in 2024.

Where is MS HAUGEN AS based?

MS HAUGEN AS has its business address in Sylte.

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.