BIZTRAC BETA
Marine fishing

BR. LUDVIGSEN AS

Org. no. 985766932 Limited company (AS) Tromsø Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 124,000
Equity NOK 15.1m
Incorporated 2003
Share capital NOK 745,000

BR. LUDVIGSEN AS is registered as a limited company in Tromsø, Troms with organisation number 985766932. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2003. Registered share capital is NOK 745,000, divided into 745 shares. The company's stated purpose is: “Kjøpe, eie og drive fiskefartøy, salg av fiskeprodukter, samt hva herved er tilknyttet, herunder erverv av andeler i selskaper, skip og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 124,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 124,000
Equity
NOK 15.1m
Est. value
NOK 8.7m

Financial health · 2024

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

Who owns BR. LUDVIGSEN AS?

SOMMARØY HOLDING AS
BR. LUDVIGSEN AS
NOK 3.6m rev. · NOK 124,000 profit

BR. LUDVIGSEN AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BR. LUDVIGSEN AS own?

BR. LUDVIGSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BR. LUDVIGSEN AS

Who owns BR. LUDVIGSEN AS?

SOMMARØY HOLDING AS is the largest registered owner, with 33.6%.

What is the revenue of BR. LUDVIGSEN AS?

BR. LUDVIGSEN AS had revenue of NOK 3.6m in 2024.

Who is the general manager of BR. LUDVIGSEN AS?

Kurt-Egil Ludvigsen is registered as general manager of BR. LUDVIGSEN AS.

Where is BR. LUDVIGSEN AS based?

BR. LUDVIGSEN AS has its business address in Sommarøya.

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.