BIZTRAC BETA
Construction of residential and non-residential buildings

HAGENBYGG AS

Org. no. 996415899 Limited company (AS) Oppdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 15.9m
Operating profit NOK 387,000
Equity NOK 1.1m
Incorporated 2011
Employees 9
Share capital NOK 100,000

HAGENBYGG AS is registered as a limited company in Oppdal, Trøndelag with organisation number 996415899. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg i egen regi og i fremmed regi samt annet som naturlig hører inn under dette, herunder investeringer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.9m in revenue and NOK 387,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.9m
Operating profit
NOK 387,000
Equity
NOK 1.1m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns HAGENBYGG AS?

E.HAGEN HOLDING AS
HAGENBYGG AS
NOK 15.9m rev. · NOK 387,000 profit

HAGENBYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HAGENBYGG AS er morselskap for 2 datterselskaper:

Frequently asked questions about HAGENBYGG AS

Who owns HAGENBYGG AS?

E.HAGEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAGENBYGG AS?

HAGENBYGG AS had revenue of NOK 15.9m in 2024.

Who is the general manager of HAGENBYGG AS?

Erlend Hagen is registered as general manager of HAGENBYGG AS.

Where is HAGENBYGG AS based?

HAGENBYGG AS has its business address in Oppdal.

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.