BIZTRAC BETA
Construction of residential and non-residential buildings

HI-BYGG AS

Org. no. 925615617 Limited company (AS) Ålesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 41.6m
Operating profit NOK 191,000
Equity NOK 1.0m
Incorporated 2020
Employees 19
Share capital NOK 1.5m

Signals

1 flags
  • Nylig endring 2026-05-12 Aksjekapital registrert 2026-05-12.

HI-BYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 925615617. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020 and has 19 registered employees. Registered share capital is NOK 1.5m, divided into 150 shares. The company's stated purpose is: “Håndverkervirksomhet og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 41.6m in revenue and NOK 191,000 in operating profit.

Key figures · 2024

Revenue
NOK 41.6m
Operating profit
NOK 191,000
Equity
NOK 1.0m
Est. value
NOK 995,000

Financial health · 2024

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

Who owns HI-BYGG AS?

HI-EIENDOM AS
HI-BYGG AS
NOK 41.6m rev. · NOK 191,000 profit

HI-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HI-BYGG AS er morselskap for 1 datterselskap:

Frequently asked questions about HI-BYGG AS

Who owns HI-BYGG AS?

HI-EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HI-BYGG AS?

HI-BYGG AS had revenue of NOK 41.6m in 2024.

Who is the general manager of HI-BYGG AS?

Odd Arne Ingebrigtsen is registered as general manager of HI-BYGG AS.

Where is HI-BYGG AS based?

HI-BYGG AS has its business address in Ålesund.

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.