BIZTRAC BETA
Drying and salting of fish

ASTRUP LOFOTEN AS

Org. no. 946366056 Limited company (AS) Værøy Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 39.5m
Operating profit NOK 173,000
Equity NOK 28.8m
Incorporated 1988
Employees 30
Share capital NOK 129,000

ASTRUP LOFOTEN AS is registered as a limited company in Værøy, Nordland with organisation number 946366056. The business is classified under drying and salting of fish (NACE 10.201). The company was incorporated in 1988 and has 30 registered employees. Registered share capital is NOK 129,000, divided into 99 shares. The company's stated purpose is: “Kjøp og salg av fisk og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.5m in revenue and NOK 173,000 in operating profit.

Key figures · 2024

Revenue
NOK 39.5m
Operating profit
NOK 173,000
Equity
NOK 28.8m
Est. value
NOK 17.8m

Financial health · 2024

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

Who owns ASTRUP LOFOTEN AS?

JARLE OTTAR ANDREASSEN
ASTRUP LOFOTEN AS
NOK 39.5m rev. · NOK 173,000 profit

ASTRUP LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ASTRUP LOFOTEN AS own?

ASTRUP LOFOTEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ASTRUP LOFOTEN AS

Who owns ASTRUP LOFOTEN AS?

JARLE OTTAR ANDREASSEN is the largest registered owner, with 50.5%.

What is the revenue of ASTRUP LOFOTEN AS?

ASTRUP LOFOTEN AS had revenue of NOK 39.5m in 2024.

Who is the general manager of ASTRUP LOFOTEN AS?

Jarle Ottar Andreassen is registered as general manager of ASTRUP LOFOTEN AS.

Where is ASTRUP LOFOTEN AS based?

ASTRUP LOFOTEN AS has its business address in Værø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.