BIZTRAC BETA
Marine fishing

ENGEBRETSEN KYSTFISKE AS

Org. no. 934988639 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 291,000
Operating profit NOK 55,000
Equity NOK 36,000
Incorporated 2025
Share capital NOK 30,000

ENGEBRETSEN KYSTFISKE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 934988639. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med hav- og kystfiske, inkludert, men ikke begrenset til, fangst, behandling og salg av sjømat, samt å tilby relaterte tjenester som utstyrsvedlikehold, logistikk og fiskerådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 291,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 291,000
Operating profit
NOK 55,000
Equity
NOK 36,000
Est. value
NOK 124,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

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

Who owns ENGEBRETSEN KYSTFISKE AS?

BENDIK HUSØY ENGEBRETSEN
ENGEBRETSEN KYSTFISKE AS
NOK 291,000 rev. · NOK 55,000 profit

ENGEBRETSEN KYSTFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGEBRETSEN KYSTFISKE AS

Who owns ENGEBRETSEN KYSTFISKE AS?

BENDIK HUSØY ENGEBRETSEN is the largest registered owner, with 100.0%.

What is the revenue of ENGEBRETSEN KYSTFISKE AS?

ENGEBRETSEN KYSTFISKE AS had revenue of NOK 291,000 in 2025.

Where is ENGEBRETSEN KYSTFISKE AS based?

ENGEBRETSEN KYSTFISKE AS has its business address in Skodje.

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.