BIZTRAC BETA
Operation of marine fish farms

LANGØYLAKS AS

Org. no. 829512572 Limited company (AS) Austevoll Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 312.6m
Operating profit NOK 44.7m
Equity NOK 196.8m
Incorporated 2022
Employees 43
Share capital NOK 100,000

LANGØYLAKS AS is registered as a limited company in Austevoll, Vestland with organisation number 829512572. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2022 and has 43 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppdrett av fisk og skalldyr, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 312.6m in revenue and NOK 44.7m in operating profit.

Key figures · 2024

Revenue
NOK 312.6m
Operating profit
NOK 44.7m
Equity
NOK 196.8m
Est. value
NOK 225.2m

Financial health · 2024

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

Who owns LANGØYLAKS AS?

LANGØYLAKS HOLDING AS
LANGØYLAKS AS
NOK 312.6m rev. · NOK 44.7m profit

LANGØYLAKS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGØYLAKS AS own?

LANGØYLAKS AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about LANGØYLAKS AS

Who owns LANGØYLAKS AS?

LANGØYLAKS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LANGØYLAKS AS?

LANGØYLAKS AS had revenue of NOK 312.6m in 2024.

Who is the general manager of LANGØYLAKS AS?

Karsten Inge Møgster is registered as general manager of LANGØYLAKS AS.

Where is LANGØYLAKS AS based?

LANGØYLAKS AS has its business address in Møkster.

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.