BIZTRAC BETA
Freezing and further processing of fish, crustaceans and molluscs

BRØDR REMØ AS

Org. no. 937600119 Limited company (AS) Sula Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 177.4m
Operating profit NOK 14.4m
Equity NOK 49.7m
Incorporated 1985
Employees 25
Share capital NOK 150,000

BRØDR REMØ AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 937600119. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 1985 and has 25 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Kjøp, produksjon og salg av fisk og fiskeprodukter av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 177.4m in revenue and NOK 14.4m in operating profit.

Key figures · 2024

Revenue
NOK 177.4m
Operating profit
NOK 14.4m
Equity
NOK 49.7m
Est. value
NOK 85.3m

Financial health · 2024

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

Who owns BRØDR REMØ AS?

AR INVEST AS
BRØDR REMØ AS
NOK 177.4m rev. · NOK 14.4m profit

BRØDR REMØ AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BRØDR REMØ AS own?

BRØDR REMØ AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BRØDR REMØ AS

Who owns BRØDR REMØ AS?

AR INVEST AS is the largest registered owner, with 36.0%.

What is the revenue of BRØDR REMØ AS?

BRØDR REMØ AS had revenue of NOK 177.4m in 2024.

Who is the general manager of BRØDR REMØ AS?

Johnny Asbjørn Remø is registered as general manager of BRØDR REMØ AS.

Where is BRØDR REMØ AS based?

BRØDR REMØ AS has its business address in Fiskarstrand.

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.