BIZTRAC BETA
Roofing activities

BLIKKENSLAGER WERNER KJOS AS

Org. no. 914822912 Limited company (AS) Arendal Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 104,000
Incorporated 2015
Share capital NOK 70,000

Signals

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

BLIKKENSLAGER WERNER KJOS AS is registered as a limited company in Arendal, Agder with organisation number 914822912. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2015. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Produksjon av blikkenslagerprodukter, utførelse av blikkenslager og ventilasjonsarbeider, samt arbeid som naturlig hører innunder slik virksomhet. Videre kan selskapet investere i aksjer og andre verdipapirer.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 104,000
Est. value
NOK 107,000

Financial health · 2025

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

Who owns BLIKKENSLAGER WERNER KJOS AS?

WERNER KJOS
BLIKKENSLAGER WERNER KJOS AS
· NOK −13,000 profit

BLIKKENSLAGER WERNER KJOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLIKKENSLAGER WERNER KJOS AS own?

BLIKKENSLAGER WERNER KJOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLIKKENSLAGER WERNER KJOS AS

Who owns BLIKKENSLAGER WERNER KJOS AS?

WERNER KJOS is the largest registered owner, with 100.0%.

Who is the general manager of BLIKKENSLAGER WERNER KJOS AS?

Werner Kjos is registered as general manager of BLIKKENSLAGER WERNER KJOS AS.

Where is BLIKKENSLAGER WERNER KJOS AS based?

BLIKKENSLAGER WERNER KJOS AS has its business address in Staubø.

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.