BIZTRAC BETA
Uoppgitt

COPELAND HOLDING AS

Org. no. 819505292 Limited company (AS) Holmestrand Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 48,000
Operating profit NOK −124,000
Equity NOK 13.3m
Incorporated 2017
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−124k kr).

COPELAND HOLDING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 819505292. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Eie og forvalte aksjer og selskapsandeler i andre selskaper, og annet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 48,000 in revenue and NOK −124,000 in operating profit.

Key figures · 2024

Revenue
NOK 48,000
Operating profit
NOK −124,000
Equity
NOK 13.3m
Est. value
NOK 22.7m

Financial health · 2024

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

Who owns COPELAND HOLDING AS?

WILLIAM SØRENSEN THORESEN
COPELAND HOLDING AS
NOK 48,000 rev. · NOK −124,000 profit

COPELAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does COPELAND HOLDING AS own?

COPELAND HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about COPELAND HOLDING AS

Who owns COPELAND HOLDING AS?

WILLIAM SØRENSEN THORESEN is the largest registered owner, with 100.0%.

What is the revenue of COPELAND HOLDING AS?

COPELAND HOLDING AS had revenue of NOK 48,000 in 2024.

Where is COPELAND HOLDING AS based?

COPELAND HOLDING AS has its business address in Holmestrand.

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.