BIZTRAC BETA
Marine fishing

STADT HAVFISKE AS

Org. no. 986885773 Limited company (AS) Stad Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 26.9m
Operating profit NOK −7.4m
Equity NOK 11.0m
Incorporated 2004
Share capital NOK 25.0m

Signals

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

STADT HAVFISKE AS is registered as a limited company in Stad, Vestland with organisation number 986885773. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2004. Registered share capital is NOK 25.0m, divided into 16650 shares. The company's stated purpose is: “Eie og drive fiskefartøyer, samt delta i andre selskaper gjennom kjøp av aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.9m in revenue and NOK −7.4m in operating profit.

Key figures · 2024

Revenue
NOK 26.9m
Operating profit
NOK −7.4m
Equity
NOK 11.0m
Est. value
NOK 10.4m

Financial health · 2024

Liquidity
1.69
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns STADT HAVFISKE AS?

ERVIK GROUP AS
STADT HAVFISKE AS
NOK 26.9m rev. · NOK −7.4m profit

STADT HAVFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STADT HAVFISKE AS

Who owns STADT HAVFISKE AS?

ERVIK GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of STADT HAVFISKE AS?

STADT HAVFISKE AS had revenue of NOK 26.9m in 2024.

Who is the general manager of STADT HAVFISKE AS?

Robert Ervik is registered as general manager of STADT HAVFISKE AS.

Where is STADT HAVFISKE AS based?

STADT HAVFISKE AS has its business address in Stadlandet.

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.