BIZTRAC BETA
Roofing activities

BLIKKENSLAGER NESSE & KARLSEN AS

Org. no. 939764488 Limited company (AS) Haugesund Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 289,000
Equity NOK 2.3m
Incorporated 1986
Share capital NOK 200,000

BLIKKENSLAGER NESSE & KARLSEN AS is registered as a limited company in Haugesund, Rogaland with organisation number 939764488. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1986. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Håndtverk og handel innen blikkenslagerfaget, samt delta i annen virksomhet med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 289,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 289,000
Equity
NOK 2.3m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns BLIKKENSLAGER NESSE & KARLSEN AS?

NOROX AS
BLIKKENSLAGER NESSE & KARLSEN AS
NOK 6.9m rev. · NOK 289,000 profit

BLIKKENSLAGER NESSE & KARLSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKENSLAGER NESSE & KARLSEN AS

Who owns BLIKKENSLAGER NESSE & KARLSEN AS?

NOROX AS is the largest registered owner, with 100.0%.

What is the revenue of BLIKKENSLAGER NESSE & KARLSEN AS?

BLIKKENSLAGER NESSE & KARLSEN AS had revenue of NOK 6.9m in 2024.

Who is the general manager of BLIKKENSLAGER NESSE & KARLSEN AS?

Paal Karlsen is registered as general manager of BLIKKENSLAGER NESSE & KARLSEN AS.

Where is BLIKKENSLAGER NESSE & KARLSEN AS based?

BLIKKENSLAGER NESSE & KARLSEN AS has its business address in Haugesund.

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.