BIZTRAC BETA
Intermediation service activities for business support service activities n.e.c.

CAPMARE AS

Org. no. 884273382 Limited company (AS) Bergen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 1.1m
Equity NOK 6.8m
Incorporated 2002
Share capital NOK 230,000

CAPMARE AS is registered as a limited company in Bergen, Vestland with organisation number 884273382. The business is classified under intermediation service activities for business support service activities n.e.c. (NACE 82.400). The company was incorporated in 2002. Registered share capital is NOK 230,000, divided into 22972 shares. The company's stated purpose is: “Investeringer i andre selskaper og rådgivende tjenester innenfor havbruk og andre tilknyttede næringer, nasjonalt og internasjonalt.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 1.1m
Equity
NOK 6.8m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns CAPMARE AS?

SOFTLAND AS
CAPMARE AS
NOK 5.9m rev. · NOK 1.1m profit

CAPMARE AS has 5 registered shareholders:

All shareholders and roles →

Which companies does CAPMARE AS own?

CAPMARE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about CAPMARE AS

Who owns CAPMARE AS?

SOFTLAND AS is the largest registered owner, with 60.1%.

What is the revenue of CAPMARE AS?

CAPMARE AS had revenue of NOK 5.9m in 2025.

Who is the general manager of CAPMARE AS?

Even Søfteland is registered as general manager of CAPMARE AS.

Where is CAPMARE AS based?

CAPMARE AS has its business address in Bergen.

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.