BIZTRAC BETA
Roofing activities

OLAF JOHNSEN & SØN AS

Org. no. 934962974 Limited company (AS) Bergen Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −875,000
Equity NOK 394,000
Incorporated 1984
Share capital NOK 100,000

Signals

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

OLAF JOHNSEN & SØN AS is registered as a limited company in Bergen, Vestland with organisation number 934962974. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1984. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Håndverksbedrift, herunder utføre kobber- og blikkenslagerarbeid og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −875,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −875,000
Equity
NOK 394,000
Est. value
NOK 922,000

Financial health · 2024

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

Who owns OLAF JOHNSEN & SØN AS?

KJELL JØRGEN JOHNSEN
OLAF JOHNSEN & SØN AS
NOK 2.2m rev. · NOK −875,000 profit

OLAF JOHNSEN & SØN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAF JOHNSEN & SØN AS

Who owns OLAF JOHNSEN & SØN AS?

KJELL JØRGEN JOHNSEN is the largest registered owner, with 100.0%.

What is the revenue of OLAF JOHNSEN & SØN AS?

OLAF JOHNSEN & SØN AS had revenue of NOK 2.2m in 2024.

Who is the general manager of OLAF JOHNSEN & SØN AS?

Kjell Jørgen Johnsen is registered as general manager of OLAF JOHNSEN & SØN AS.

Where is OLAF JOHNSEN & SØN AS based?

OLAF JOHNSEN & SØN AS has its business address in Nesttun.

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.