BIZTRAC BETA
Manufacture of veneer sheets and wood-based panels

CL3 NORGE AS

Org. no. 930030252 Limited company (AS) Tvedestrand Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −4.2m
Equity NOK 2.5m
Incorporated 2022
Share capital NOK 4.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,2 mill kr).

CL3 NORGE AS is registered as a limited company in Tvedestrand, Agder with organisation number 930030252. The business is classified under manufacture of veneer sheets and wood-based panels (NACE 16.210). The company was incorporated in 2022. Registered share capital is NOK 4.2m, divided into 417500 shares. The company's stated purpose is: “Produksjon og salg av krysslimte plater.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −4.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −4.2m
Equity
NOK 2.5m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns CL3 NORGE AS?

LINDAL GRUPPEN AS
CL3 NORGE AS
NOK 1.9m rev. · NOK −4.2m profit

CL3 NORGE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CL3 NORGE AS own?

CL3 NORGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CL3 NORGE AS

Who owns CL3 NORGE AS?

LINDAL GRUPPEN AS is the largest registered owner, with 61.4%.

What is the revenue of CL3 NORGE AS?

CL3 NORGE AS had revenue of NOK 1.9m in 2024.

Who is the general manager of CL3 NORGE AS?

Håkon Stenberg Rognlien is registered as general manager of CL3 NORGE AS.

Where is CL3 NORGE AS based?

CL3 NORGE AS has its business address in Tvedestrand.

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.