BIZTRAC BETA
COMPANY REGISTER PROFILE
916031254 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Roofing activities

BRØNNØY BLIKK AS

Org. no. 916031254 Limited company (AS) Alstahaug Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 9.2m
Operating profit NOK 473,000
Equity NOK 4.2m
Incorporated 2015
Employees 12
Share capital NOK 30,000

BRØNNØY BLIKK AS is registered as a limited company in Alstahaug, Nordland with organisation number 916031254. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2015 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Blikkenslager og ventilasjonsarbeid, samt deltakelse i andre selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.2m in revenue and NOK 473,000 in operating profit.

Former names: BRØNNØY BLIKK 1 AS

Key figures · 2025

Revenue
NOK 9.2m
▼ −3 %
Operating profit
NOK 473,000
▼ −22 %
Equity
NOK 4.2m
▲ +10 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
4.60
Very good
Current assets ÷ current liabilities
Profitability
8.9%
Satisfactory
Return on total assets
Solidity
79.3%
Very good
Equity as a share of total capital

Who owns BRØNNØY BLIKK AS?

BRØNNØY BLIKK AS
NOK 9.2m rev. · NOK 473,000 profit

BRØNNØY BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRØNNØY BLIKK AS

Who owns BRØNNØY BLIKK AS?

ÅSVANG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRØNNØY BLIKK AS?

BRØNNØY BLIKK AS had revenue of NOK 9.2m in 2025.

Who is the general manager of BRØNNØY BLIKK AS?

Arnt Jørgen Tro Åsvang is registered as general manager of BRØNNØY BLIKK AS.

Where is BRØNNØY BLIKK AS based?

BRØNNØY BLIKK AS has its business address in Sandnessjøen.

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

Report a problem

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