BIZTRAC BETA
Masonry and bricklaying activities

JOHANNESSEN OG HAGEN AS

Org. no. 976203453 Limited company (AS) Trondheim Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 23.7m
Operating profit NOK 1.7m
Equity NOK 2.4m
Incorporated 1996
Employees 20
Share capital NOK 350,000

JOHANNESSEN OG HAGEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 976203453. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1996 and has 20 registered employees. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Entreprenørvirksomhet innen overflatebehandling, herunder murertjenester, samt relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.7m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 23.7m
Operating profit
NOK 1.7m
Equity
NOK 2.4m
Est. value
NOK 6.8m

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.8%
Good
Equity as a share of total capital

Who owns JOHANNESSEN OG HAGEN AS?

HG HÅNDVERKSGRUPPEN NORGE AS
JOHANNESSEN OG HAGEN AS
NOK 23.7m rev. · NOK 1.7m profit

JOHANNESSEN OG HAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHANNESSEN OG HAGEN AS

Who owns JOHANNESSEN OG HAGEN AS?

HG HÅNDVERKSGRUPPEN NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of JOHANNESSEN OG HAGEN AS?

JOHANNESSEN OG HAGEN AS had revenue of NOK 23.7m in 2024.

Who is the general manager of JOHANNESSEN OG HAGEN AS?

Erlend Johannessen is registered as general manager of JOHANNESSEN OG HAGEN AS.

Where is JOHANNESSEN OG HAGEN AS based?

JOHANNESSEN OG HAGEN AS has its business address in Heimdal.

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.