BIZTRAC BETA
Marine fishing

LURØYVEIDING AS

Org. no. 974379066 Limited company (AS) Lurøy Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 135.0m
Operating profit NOK 49.8m
Equity NOK 176.2m
Incorporated 1995
Employees 23
Share capital NOK 572,000

LURØYVEIDING AS is registered as a limited company in Lurøy, Nordland with organisation number 974379066. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1995 and has 23 registered employees. Registered share capital is NOK 572,000, divided into 1429 shares. The company's stated purpose is: “Eie og drive fartøy for fangst og fiske, forretningsmessig foredling av næringsmiddel, herunder være interesent i tilsvarende forretningsområde.”. The most recent filed accounts, for the 2025 financial year, show NOK 135.0m in revenue and NOK 49.8m in operating profit.

Key figures · 2025

Revenue
NOK 135.0m
Operating profit
NOK 49.8m
Equity
NOK 176.2m
Est. value
NOK 214.4m

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.4%
Good
Equity as a share of total capital

Who owns LURØYVEIDING AS?

THOMAS SELNES JOHANSEN
LURØYVEIDING AS
NOK 135.0m rev. · NOK 49.8m profit

LURØYVEIDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LURØYVEIDING AS own?

LURØYVEIDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LURØYVEIDING AS

Who owns LURØYVEIDING AS?

THOMAS SELNES JOHANSEN is the largest registered owner, with 58.6%.

What is the revenue of LURØYVEIDING AS?

LURØYVEIDING AS had revenue of NOK 135.0m in 2025.

Who is the general manager of LURØYVEIDING AS?

Rose-Mari Berge is registered as general manager of LURØYVEIDING AS.

Where is LURØYVEIDING AS based?

LURØYVEIDING AS has its business address in Lurø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.