BIZTRAC BETA
Roofing activities

BLIKKENSLAGEREN AS

Org. no. 951763624 Limited company (AS) Ålesund Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −36,000
Equity NOK 458,000
Incorporated 1989
Share capital NOK 100,000

Signals

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

BLIKKENSLAGEREN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 951763624. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Blikkenslagervirksomhet, samt handel og hva som herved naturlig står i forbindelse, samt deltag- else ved aksjeinnskudd eller på annen måte i sel- skaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 458,000
Est. value
NOK 470,000

Financial health · 2024

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

Who owns BLIKKENSLAGEREN AS?

BJØRN-IVAR HELGESEN
BLIKKENSLAGEREN AS
NOK 0 rev. · NOK −36,000 profit

BLIKKENSLAGEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKENSLAGEREN AS

Who owns BLIKKENSLAGEREN AS?

BJØRN-IVAR HELGESEN is the largest registered owner, with 100.0%.

What is the revenue of BLIKKENSLAGEREN AS?

BLIKKENSLAGEREN AS had revenue of NOK 0 in 2024.

Who is the general manager of BLIKKENSLAGEREN AS?

Bjørn-Ivar Helgesen is registered as general manager of BLIKKENSLAGEREN AS.

Where is BLIKKENSLAGEREN AS based?

BLIKKENSLAGEREN AS has its business address in Ålesund.

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.