BIZTRAC BETA
Joinery installation

CHAM HOLDING AS

Org. no. 930584894 Limited company (AS) Porsgrunn Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 41,000
Operating profit NOK −73,000
Equity NOK 50,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

CHAM HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 930584894. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i andre selskaper, kjøp og salg av aksjer og annen drift som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 41,000 in revenue and NOK −73,000 in operating profit.

Key figures · 2024

Revenue
NOK 41,000
Operating profit
NOK −73,000
Equity
NOK 50,000
Est. value
NOK 24,000

Financial health · 2024

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

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

Who owns CHAM HOLDING AS?

TOM EGIL CHAM
CHAM HOLDING AS
NOK 41,000 rev. · NOK −73,000 profit

CHAM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHAM HOLDING AS own?

CHAM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CHAM HOLDING AS

Who owns CHAM HOLDING AS?

TOM EGIL CHAM is the largest registered owner, with 100.0%.

What is the revenue of CHAM HOLDING AS?

CHAM HOLDING AS had revenue of NOK 41,000 in 2024.

Where is CHAM HOLDING AS based?

CHAM HOLDING AS has its business address in Porsgrunn.

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.