BIZTRAC BETA
Operation of freshwater hatcheries

LØDINGEN FISK AS

Org. no. 884625882 Limited company (AS) Lødingen Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 86.9m
Operating profit NOK 17.0m
Equity NOK 88.0m
Incorporated 2002
Employees 32
Share capital NOK 13.9m

Signals

1 flags
  • Nylig endring 2026-03-27 Aksjekapital registrert 2026-03-27.

LØDINGEN FISK AS is registered as a limited company in Lødingen, Nordland with organisation number 884625882. The business is classified under operation of freshwater hatcheries (NACE 03.222). The company was incorporated in 2002 and has 32 registered employees. Registered share capital is NOK 13.9m, divided into 139201 shares. The company's stated purpose is: “Produksjon og salg av yngel av anadrom og marin fisk med tilhørende virksomhet, herunder også deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 86.9m in revenue and NOK 17.0m in operating profit.

Key figures · 2024

Revenue
NOK 86.9m
Operating profit
NOK 17.0m
Equity
NOK 88.0m
Est. value
NOK 89.6m

Financial health · 2024

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

Who owns LØDINGEN FISK AS?

ØYFISK AS
LØDINGEN FISK AS
NOK 86.9m rev. · NOK 17.0m profit

LØDINGEN FISK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØDINGEN FISK AS

Who owns LØDINGEN FISK AS?

ØYFISK AS is the largest registered owner, with 48.3%.

What is the revenue of LØDINGEN FISK AS?

LØDINGEN FISK AS had revenue of NOK 86.9m in 2024.

Who is the general manager of LØDINGEN FISK AS?

Truls Olsen is registered as general manager of LØDINGEN FISK AS.

Where is LØDINGEN FISK AS based?

LØDINGEN FISK AS has its business address in Vestbygda.

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.