BIZTRAC BETA
Freezing and further processing of fish, crustaceans and molluscs

OLE LØVOLD AS

Org. no. 929445260 Limited company (AS) Averøy Incorporated 1980 Active
Ownership graph ↗
Revenue 2024 NOK 39.4m
Operating profit NOK 6.6m
Equity NOK 38.9m
Incorporated 1980
Employees 22
Share capital NOK 561,000

OLE LØVOLD AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 929445260. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 1980 and has 22 registered employees. Registered share capital is NOK 561,000, divided into 561 shares. The company's stated purpose is: “Kjøp, foredling og salg av fiskeprodukter og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.4m in revenue and NOK 6.6m in operating profit.

Key figures · 2024

Revenue
NOK 39.4m
Operating profit
NOK 6.6m
Equity
NOK 38.9m
Est. value
NOK 45.9m

Financial health · 2024

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

Who owns OLE LØVOLD AS?

LØVOLD HOLDING AS
OLE LØVOLD AS
NOK 39.4m rev. · NOK 6.6m profit

OLE LØVOLD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLE LØVOLD AS own?

OLE LØVOLD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OLE LØVOLD AS

Who owns OLE LØVOLD AS?

LØVOLD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OLE LØVOLD AS?

OLE LØVOLD AS had revenue of NOK 39.4m in 2024.

Who is the general manager of OLE LØVOLD AS?

Ole Løvold is registered as general manager of OLE LØVOLD AS.

Where is OLE LØVOLD AS based?

OLE LØVOLD AS has its business address in Averøy.

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.