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

BLIKKHJØRNET AS

Org. no. 984350082 Limited company (AS) Årdal Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 573,000
Equity NOK 2.6m
Incorporated 2002
Share capital NOK 200,000

BLIKKHJØRNET AS is registered as a limited company in Årdal, Vestland with organisation number 984350082. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Montering, produksjon og salg av tynnplate produkt og det som hører inn under dette. Selskapet kan også delta som aksjonær, eller på annen måte ved investering i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 573,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
▼ −6 %
Operating profit
NOK 573,000
▲ +123 %
Equity
NOK 2.6m
▲ +32 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
4.80
Very good
Current assets ÷ current liabilities
Profitability
14.3%
Good
Return on total assets
Solidity
62.9%
Very good
Equity as a share of total capital

Who owns BLIKKHJØRNET AS?

BLIKKHJØRNET AS
NOK 4.7m rev. · NOK 573,000 profit

BLIKKHJØRNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKHJØRNET AS

Who owns BLIKKHJØRNET AS?

EMIL GEIR BRONNES is the largest registered owner, with 100.0%.

What is the revenue of BLIKKHJØRNET AS?

BLIKKHJØRNET AS had revenue of NOK 4.7m in 2025.

Who is the general manager of BLIKKHJØRNET AS?

Emil Geir Bronnes is registered as general manager of BLIKKHJØRNET AS.

Where is BLIKKHJØRNET AS based?

BLIKKHJØRNET AS has its business address in Øvre Årdal.

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.