BIZTRAC BETA
Operation of marine fish farms

LERØY VEST AS

Org. no. 886813082 Limited company (AS) Austevoll Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 2.6bn
Operating profit NOK 224.1m
Equity NOK 1.9bn
Incorporated 2004
Employees 240
Share capital NOK 830,000

LERØY VEST AS is registered as a limited company in Austevoll, Vestland with organisation number 886813082. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2004 and has 240 registered employees. Registered share capital is NOK 830,000, divided into 4148 shares. The company's stated purpose is: “Fiskeoppdrett og hva dermed står i forbindelse, samt å eie aksjer i selskap med lignende eller annet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6bn in revenue and NOK 224.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.6bn
Operating profit
NOK 224.1m
Equity
NOK 1.9bn
Est. value
NOK 1.7bn

Financial health · 2024

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

Who owns LERØY VEST AS?

LERØY SEAFOOD GROUP ASA
LERØY VEST AS
NOK 2.6bn rev. · NOK 224.1m profit

LERØY VEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LERØY VEST AS own?

LERØY VEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LERØY VEST AS

Who owns LERØY VEST AS?

LERØY SEAFOOD GROUP ASA is the largest registered owner, with 100.0%.

What is the revenue of LERØY VEST AS?

LERØY VEST AS had revenue of NOK 2.6bn in 2024.

Who is the general manager of LERØY VEST AS?

Morten Egenæs Fjæreide is registered as general manager of LERØY VEST AS.

Where is LERØY VEST AS based?

LERØY VEST AS has its business address in Storebø.

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.