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

CAFLO SALMON AS

Org. no. 925181730 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 3,000
Incorporated 2020
Share capital NOK 30,000

CAFLO SALMON AS is registered as a limited company in Oslo, Oslo with organisation number 925181730. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Foredling av laks og andre fiskeprodukter, andre produkter og tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 3,000
Est. value
NOK 3,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CAFLO SALMON AS?

CAFLO ASSET MANAGEMENT AS
CAFLO SALMON AS
NOK 0 rev. · NOK 0 profit

CAFLO SALMON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAFLO SALMON AS

Who owns CAFLO SALMON AS?

CAFLO ASSET MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of CAFLO SALMON AS?

CAFLO SALMON AS had revenue of NOK 0 in 2025.

Where is CAFLO SALMON AS based?

CAFLO SALMON AS has its business address in Oslo.

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.