biztrac. BETA
COMPANY REGISTER PROFILE
884625882 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Operation of freshwater hatcheries

LØDINGEN FISK AS

Org. no. 884625882 Limited company (AS) Lødingen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 89.3m
Operating profit NOK 13.3m
Equity NOK 166.4m
Incorporated 2002
Employees 34
Share capital NOK 13.9m

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 34 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 2025 financial year, show NOK 89.3m in revenue and NOK 13.3m in operating profit.

Key figures · 2025

Revenue
NOK 89.3m
▲ +3 %
Operating profit
NOK 13.3m
▼ −22 %
Equity
NOK 166.4m
▲ +89 %
Est. value
NOK 118.2m

Financial health · 2025

Liquidity
7.42
Very good
Current assets ÷ current liabilities
Profitability
7.0%
Satisfactory
Return on total assets
Solidity
73.9%
Very good
Equity as a share of total capital

Who owns LØDINGEN FISK AS?

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 89.3m in 2025.

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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.