BIZTRAC BETA
Roofing activities

BLIKKENSLAGER JØRN HELGE BERNES AS

Org. no. 914900441 Limited company (AS) Austrheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 386,000
Equity NOK 600,000
Incorporated 2015
Share capital NOK 30,000

BLIKKENSLAGER JØRN HELGE BERNES AS is registered as a limited company in Austrheim, Vestland with organisation number 914900441. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Virksomhet innen bygg og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 386,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 386,000
Equity
NOK 600,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns BLIKKENSLAGER JØRN HELGE BERNES AS?

JØRN HELGE BERNES
BLIKKENSLAGER JØRN HELGE BERNES AS
NOK 2.9m rev. · NOK 386,000 profit

BLIKKENSLAGER JØRN HELGE BERNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKENSLAGER JØRN HELGE BERNES AS

Who owns BLIKKENSLAGER JØRN HELGE BERNES AS?

JØRN HELGE BERNES is the largest registered owner, with 100.0%.

What is the revenue of BLIKKENSLAGER JØRN HELGE BERNES AS?

BLIKKENSLAGER JØRN HELGE BERNES AS had revenue of NOK 2.9m in 2025.

Who is the general manager of BLIKKENSLAGER JØRN HELGE BERNES AS?

Jørn Helge Bernes is registered as general manager of BLIKKENSLAGER JØRN HELGE BERNES AS.

Where is BLIKKENSLAGER JØRN HELGE BERNES AS based?

BLIKKENSLAGER JØRN HELGE BERNES AS has its business address in Austrheim.

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.