biztrac. BETA
COMPANY REGISTER PROFILE
996692329 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

CANCOATING AS

Org. no. 996692329 Limited company (AS) Drammen Incorporated 2011 Active
Revenue 2025 NOK 1.1m
Operating profit NOK −27,000
Equity NOK 1.1m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).

CANCOATING AS is registered as a limited company in Drammen, Buskerud with organisation number 996692329. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av konsulenttjenester innenfor området industrilakker og plast. Investorvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▼ −56 %
Operating profit
NOK −27,000
▼ −103 %
Equity
NOK 1.1m
▲ +2 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
6.20
Very good
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
83.9%
Very good
Equity as a share of total capital

Who owns CANCOATING AS?

CANCOATING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about CANCOATING AS

Who owns CANCOATING AS?

Siri Furevik Norhagen is the largest registered owner, with 49.0%.

What is the revenue of CANCOATING AS?

CANCOATING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of CANCOATING AS?

Gunnar Alf Furevik is registered as general manager of CANCOATING AS.

Where is CANCOATING AS based?

CANCOATING AS has its business address in Krokstadelva.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.